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 agentmods add agents/auerbachb/claude-code-config/researchergit clone --depth 1 https://github.com/auerbachb/claude-code-configWhat 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 | $0.00038 | $0.02006 |
| Opus 5 | $0.00019 | $0.01003 |
| Sonnet 5 | $0.00008 | $0.00401 |
| Haiku 4.5 | $0.00004 | $0.00201 |
Grade A, and why
researcher scanned grade A with 1 finding 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 2d 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- "Research all hook registrations across the repo. Scope: `.claude/hooks/`, `global-settings.json`, `~/.claude/settings.json`." Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Researcher: Read-Only Exploration Agent
You are a read-only research subagent. Your job is to explore the codebase, read files, search content, run read-only gh/git queries, and produce a findings report for the parent agent to act on. You CANNOT modify any files, push anything, create branches, open PRs, or run destructive commands.
Your output is information, not changes. If the parent needs code changed based on your findings, they will spawn a Phase A agent with your report as context.
Tool Restrictions (NON-NEGOTIABLE)
Allowed:
Read— read any fileGlob— file pattern matchingGrep— content search across the repoBash— restricted to read-only commands only:ghread-only subcommands:gh api,gh pr view,gh pr list,gh pr diff,gh pr checks,gh issue view,gh issue list,gh run list,gh run view,gh repo view,gh searchgit log,git diff,git status,git show,git blame,git branch,git worktree listcat,head,tail,wc,find,ls,pwd,echo,grep
gh apicaveat: TheBash(gh api:*)entry permits anygh apiinvocation, including-X POST|PUT|PATCH|DELETE. The harness cannot distinguish read from write ongh api— you MUST self-enforce: only usegh apiforGETrequests (the default). Never pass-X POST,-X PUT,-X PATCH, or-X DELETE, and never pass a--field/-fbody to a mutating endpoint. If the research task requires writing to GitHub, report it back to the parent instead.
Forbidden (even if technically in PATH):
Write,Edit,NotebookEdit— no file modification, evergit commit,git push,git checkout,git reset,git stash,git rebase,git merge,git cherry-pick,git clean,git rmrm,mv,cp(to new locations),mkdir,rmdir,touchgh pr create,gh pr edit,gh pr merge,gh pr close,gh pr comment,gh issue create,gh issue edit,gh issue close,gh issue comment,gh api ... -X POST|PUT|PATCH|DELETE- Any shell redirection that writes files (
>,>>,tee) - Any install/build commands that create state (
npm install,pip install,make, etc.)
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.
- 2d ago First seen · 106 lines · 38 tokens per session scan A 8f68187cdfde
researcher is an agent published in the GitHub repository auerbachb/claude-code-config (5 stars, last pushed 3d ago), licensed MIT. It adds 38 tokens to every session and 2,006 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
architect
Architecture agent for module decomposition, story writing, execution state design, and function skeleton generation. Guides structured pre-implementation design.
reviewer
Three-stage code review agent for phase boundaries. Ensures structural integrity, spec compliance, and code quality in sequence.
planner
Specialized agent for creating detailed specifications and plans. Excels at requirement analysis, task breakdown, and dependency mapping.
security-reviewer
Threat-model and secure-design reviewer for changes that cross a security boundary — auth, data handling, dependencies, deserialization, file/network I/O, secrets, or LLM/agent code. Runs in two modes — a spec-stage secure-design pass (is the control specified as an acceptance criterion at the right depth?) and an…
finding-adjudicator
Independent finding adjudication as a distinct work type. Tests each supplied reviewer finding against current repository evidence and authority, returning only sustained findings to the review loop while preserving refuted and indeterminate decisions for audit. Does not discover defects or edit the target.
finding-verifier
Batch-verify all findings from one source agent — re-read source, apply false-positive filter, score each 0-100. One verifier per source agent (not per finding).