Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add theshubh007/agent-skill-finder --skill gitleaks-secret-detectorgit clone --depth 1 https://github.com/theshubh007/agent-skill-finderWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/theshubh007/agent-skill-finder/gitleaks-secret-detector)<a href="https://agentmods.dev/skills/theshubh007/agent-skill-finder/gitleaks-secret-detector"><img src="https://agentmods.dev/badge/skills/theshubh007/agent-skill-finder/gitleaks-secret-detector/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/theshubh007/agent-skill-finder/gitleaks-secret-detector"><img src="https://agentmods.dev/badge/skills/theshubh007/agent-skill-finder/gitleaks-secret-detector.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00073 | $0.00607 |
| Opus 5.5 | $0.00029 | $0.00243 |
| Sonnet 5.5 | $0.00015 | $0.00121 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
Gitleaks Secret Detector scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
What this skill does
Runs gitleaks detect against a local git repository and parses the JSON output
into structured findings. Each finding reports the rule ID, the type of credential
detected, the file and line number, and a redacted match preview. Never returns
the full unredacted secret value.
Inputs
repo_path— absolute or relative path to the git repository rootconfig_path— optional path to a custom.gitleaks.tomlallowlist configbranch— optional branch name or commit SHA to scan (default: current HEAD)
Outputs
findings— list of{rule_id, file, line_number, secret_type, redacted_match, commit}objectstotal_count— total number of secrets detectedclean—truewhentotal_count == 0
Example
gitleaks detect --source . --report-format json --report-path findings.json
{
"findings": [
{
"rule_id": "aws-access-token",
"file": "scripts/deploy.sh",
"line_number": 14,
"secret_type": "AWS Access Key ID",
"redacted_match": "AKIA***XYZ",
"commit": "a3f2c1d"
}
],
"total_count": 1,
"clean": false
}
Notes
- Requires
gitleaksbinary on PATH (brew install gitleaksor download from GitHub releases) - Use
config_pathto add allowlist entries for test fixtures or known false positives - Output never includes the full unredacted secret — only the redacted preview
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 80 lines · 73 tokens per session scan A a42a1180e070
Gitleaks Secret Detector is a skill published in the GitHub repository theshubh007/agent-skill-finder (12 stars, last pushed 6mo ago), licensed MIT. It adds 73 tokens to every session and 607 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Gitleaks Secret Detector compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| Gitleaks Secret Detectortheshubh007/agent-skill-finder | Skill | 12 | 6mo ago | MIT | A | 73 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 135k | today | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 100k | today | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 395k | today | MIT | A | 36 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 80k | 9d ago | MIT | A | 200 | Claude Code, Codex |
| next-cache-components-adoptionvercel/next.js | Skill | 144k | today | MIT | A | 95 | Claude Code |
| chroniclemicrosoft/vscode | Skill | 195k | today | MIT | A | 72 | Claude Code, Codex |