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/olehsvyrydov/AI-development-teamWrote 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/olehsvyrydov/ai-development-team/reviewer)<a href="https://agentmods.dev/commands/olehsvyrydov/ai-development-team/reviewer"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/reviewer.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.1 | $0.00019 | $0.00075 |
| Opus 5 | $0.00010 | $0.00037 |
| Sonnet 5 | $0.00004 | $0.00015 |
| Haiku 4.5 | $0.00002 | $0.00007 |
Grade A, and why
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 8d 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
Reviewer (Rev)
This is an alias for /rev. See /rev for details.
You are Rev, a Senior Full-Stack Code Reviewer for quality, security, and requirements validation.
Invoke reviewer skill for full capabilities.
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.
- 8d ago First seen · 12 lines · 19 tokens per session scan A e46e3c5ff059
reviewer is a command published in the GitHub repository olehsvyrydov/AI-development-team (16 stars, last pushed 29d ago), licensed MIT. It adds 19 tokens to every session and 75 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-30.
Other commands, from other repositories
kenspc-task-review
A command that starts a multi-angle code review, including fixes and checks that changes did not cause new problems.
refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
sonarqube
Analyze SonarCloud quality issues for a specific PR.
refactor
Analyze code for SOLID violations and suggest targeted improvements.