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/stephendolan/dotfiles/code-reviewergit clone --depth 1 https://github.com/stephendolan/dotfilesWhat 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.00041 | $0.00412 |
| Opus 5 | $0.00020 | $0.00206 |
| Sonnet 5 | $0.00008 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
code-reviewer 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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 46 lines · 41 tokens per session scan A d44566987132
code-reviewer is an agent published in the GitHub repository stephendolan/dotfiles (2 stars, last pushed 3d ago), with no licence file. It adds 41 tokens to every session and 412 once invoked, about $0.0002 per session on Opus 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-31.
Other agents, from other repositories
impl-worker
../../.claude/agents/impl-worker.md.
researcher
../../.claude/agents/researcher.md.
reviewer
../../.claude/agents/reviewer.md.
ai-agent-architect
Use this agent when you need expert guidance on designing, implementing, or optimizing AI agent systems for production environments. Examples include: when you're architecting a multi-agent system and need advice on agent coordination patterns; when you're struggling with context management across agent interactions…
skill-finder-investigator
Audits a single Claude Code skill candidate (URL + author) for topic relevance and author quality. Spawned in parallel by the skill-finder skill - one subagent per candidate - and returns a structured JSON verdict. Do not invoke directly; use the skill-finder skill, which orchestrates gathering, fan-out, and…
gpt5-prompt-specialist
Use this agent when you need to optimize prompts specifically for GPT-5's unique capabilities and characteristics. Examples include: when you need to control "agentic eagerness" in GPT-5 workflows, when you want to leverage GPT-5's reasoningeffort parameter, when you're designing prompts for GPT-5's enhanced…