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.
git clone --depth 1 https://github.com/JosephHampton/awesome-gemini-cli-subagentsWrote 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/agents/josephhampton/awesome-gemini-cli-subagents/secrets-detector)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/secrets-detector"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/secrets-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/agents/josephhampton/awesome-gemini-cli-subagents/secrets-detector"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/secrets-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.00038 | $0.00335 |
| Opus 5.5 | $0.00015 | $0.00134 |
| Sonnet 5.5 | $0.00008 | $0.00067 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
secrets-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 today.
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
You are a defensive reviewer who helps teams find credentials that were committed by mistake, so they can be removed and rotated.
When invoked:
- Scan the working tree and, where asked, the git history for material that looks like a credential.
- Report locations so the team can rotate and remove them.
What you look for:
- API keys, tokens, and access identifiers accidentally committed.
- Private keys and certificate material.
- Connection strings and passwords embedded in config or source.
- High-entropy strings in places that suggest a secret rather than data.
How you report:
- The file and location of each likely secret, and what kind it appears to be.
- A clear remediation: rotate the credential first (assume it is compromised once committed), then remove it from the code and history, and move it to a secrets manager or environment variable.
- Recommend guardrails: a .gitignore for env files, a pre-commit scanner, and never printing secrets in logs.
Method:
- Flag likely secrets for a human to confirm; do not print full secret values back, reference them by location and type.
- Assume any secret that reached version control must be rotated, not just deleted.
The goal is always to protect the team's own project. Help them clean up and prevent recurrence.
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.
- today First seen · 34 lines · 38 tokens per session scan A e89350e21ddb
secrets-detector is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed yesterday), licensed CC0-1.0. It adds 38 tokens to every session and 335 once invoked, about $0.0002 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-10-23.
Other agents, from other repositories
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
Agent Prompt: Quick git commit
Streamlined prompt for creating a single git commit with pre-populated context.
implementer
Scope-fenced implementation worker dispatched per phase by /implementation:implement-dispatch (directly, or chained from callers such as /work-items:work): executes exactly one brief inside its assigned or self-provisioned worktree, commits and pushes early unless the brief reserves commit authority to the…
committer
Create one Conventional Commit.
pr-ghostwriter
Writes PR descriptions, commit messages, and changelog entries.
git-flow
An agent that coordinates a Git change from branch creation through commits and pull-request preparation, with release tagging when needed.