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 commands/citedy/skills/code-review-teamgit clone --depth 1 https://github.com/citedy/skillsWrote 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/commands/citedy/skills/code-review-team)<a href="https://agentmods.dev/commands/citedy/skills/code-review-team"><img src="https://agentmods.dev/badge/commands/citedy/skills/code-review-team.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.00095 |
| Opus 5 | $0.00009 | $0.00048 |
| Sonnet 5 | $0.00003 | $0.00019 |
| Haiku 4.5 | $0.00002 | $0.00010 |
Grade A, and why
code-review-team 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 3d 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
Treat $1 as optional PR number or review target.
Read .claude/skills/code-review-agent-team/SKILL.md and follow the full workflow:
- Determine review target (uncommitted, staged, PR, last commit)
- Capture diff
- Spawn 4 reviewer agents in parallel
- Collect findings and present unified report
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.
- 3d ago First seen · 11 lines · 17 tokens per session scan A 41e1501d3710
code-review-team is a command published in the GitHub repository citedy/skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 95 once invoked, about $0.0001 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 commands, from other repositories
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
save
Save this conversation as a new or existing reusable context.
deps-age
Analyze dependency freshness and maintenance activity.
setup
Diagnose-first project setup with state machine — scans, confirms, interviews, writes.
scan
Scan AWS account for cost optimization.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.