secrets

Scan files, endpoints, and repositories for exposed secrets and credentials.

18|3|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Kalp1774/akira --skill secrets-kalp1774
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secrets
Source: https://github.com/Kalp1774/akira/tree/main/skills/secrets
Command: npx skills add https://github.com/Kalp1774/akira --skill secrets-kalp1774

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and verifies exposed secrets, API keys, tokens, and credentials within a pentest target to reduce noisy findings and ensure every reported secret has supporting evidence.

Core Features & Use Cases

  • Scoped Secrets Scanning: Runs trufflehog/gitleaks against recon-provided URLs and live hosts to find high-confidence secrets.
  • Evidence-Gated Verification: Focuses on verified findings and produces a concise interesting_secrets.md summarizing confirmed and potential secrets.
  • Supplementary Hunting: Performs GitHub dorking and API/Postman spec discovery to expand the search surface and extract endpoints for later exploitation or analysis.
  • Operational Integration: Writes results into the pentest toolkit results directory and updates session.json to hand off credentials to downstream phases.

Quick Start

Run the secrets skill to scan the target using available recon scope and produce a verified interesting_secrets.md that updates session.json.

Frequently Asked Questions about secrets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find exposed API keys and credentials during a penetration test?

Exposed secrets are identified by scanning JavaScript files and repository artifacts with trufflehog and gitleaks, then performing GitHub dorking and API spec discovery. It verifies findings to reduce noise and produces an interesting_secrets.md summary with supporting evidence.

How do I verify exposed secrets to reduce noisy pentest findings?

Verifying exposed secrets involves evidence-gated checks on trufflehog and gitleaks outputs against live hosts. This Skill focuses on confirmed findings to reduce noise, producing a concise interesting_secrets.md that summarizes verified credentials with supporting evidence.

Can I use trufflehog and gitleaks outputs for credential hunting on a specific scope?

Yes, trufflehog and gitleaks outputs can be used for credential hunting. This Skill accepts those outputs alongside optional gh CLI results, scanning recon-provided URLs and live hosts to extract endpoints and hand off discovered credentials to downstream pentest phases.

What is GitHub dorking and how does it help discover exposed API keys?

GitHub dorking searches repositories for sensitive patterns to expand the credential hunting surface. It complements trufflehog and gitleaks scans by extracting endpoints and discovering API or Postman specs for later exploitation and analysis.

Does this approach discover API and Postman spec paths for credential extraction?

Yes, this approach probes common API and Postman spec paths to expand the search surface. It extracts endpoints from these specs for later exploitation, adding supplementary hunting results to the verified interesting_secrets.md findings summary.

How do I integrate discovered credentials into a pentest toolkit session?

Integrating discovered credentials involves writing results into the pentest toolkit results directory and updating session.json. This operational integration hands off verified credentials to downstream phases, ensuring every reported secret has supporting evidence.