Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/skills/mountainunicorn/add/reviewer)<a href="https://agentmods.dev/skills/mountainunicorn/add/reviewer"><img src="https://agentmods.dev/badge/skills/mountainunicorn/add/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.00018 | $0.04505 |
| Opus 5 | $0.00009 | $0.02253 |
| Sonnet 5 | $0.00004 | $0.00901 |
| Haiku 4.5 | $0.00002 | $0.00451 |
Grade A, and why
reviewer 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 6d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Search for synchronous I/O in async contexts (`readFileSync`, `execSync`, blocking HTTP calls) How it starts
The opening of the file, as written. The whole thing — 631 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADD Reviewer Skill v{{VERSION}}
Conduct a comprehensive code review focused on specification compliance, code quality, and ADD methodology adherence. This is a READ-ONLY skill that produces a detailed structured review report.
Overview
The Reviewer analyzes implementation against the spec and quality standards without modifying code. It checks:
- Spec Compliance: Every acceptance criterion has a corresponding passing test
- Code Quality: Readability, maintainability, style adherence
- Test Coverage: Edge cases, error conditions, user scenarios
- Architecture: Separation of concerns, dependency management
- Error Handling: Validation, exception handling, error messages
- Documentation: Comments, docstrings, API clarity
- ADD Adherence: Test coverage, traceability, naming conventions
Pre-Flight Checks
-
Verify spec file exists
- Read spec at provided path
- Extract feature name, acceptance criteria, user test cases
- Identify scope (backend, frontend, or full system)
-
Verify implementation exists
- Locate implementation files from spec or config
- Verify code files are readable
- Check for completeness (no placeholder files)
-
Verify tests exist and pass
- Locate test files (tests/ or tests/)
- Read test mapping file if available
- Run tests to confirm all passing:
npm testorpython -m pytest - Halt if tests not passing (code not GREEN)
-
Load configuration
- Read .add/config.json for:
- Code style rules
- Test coverage thresholds
- Quality standards
- Naming conventions
- Read .add/config.json for:
-
Determine review scope
- Use --scope flag or infer from config
- backend: Server, API, database code
- frontend: UI, components, client code
- full: Everything
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.
- 6d ago First seen · 631 lines · 18 tokens per session scan A 5fff83b70470
reviewer is a skill published in the GitHub repository MountainUnicorn/add (11 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 4,505 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
swarm
Launching multi-agent parallel work with the Agentic SDLC. Use when a task benefits from decomposition into parallel subtasks.
finish
Completing a development branch for merge readiness. Use when implementation and tests pass and the branch needs formal preparation for review and merge.
grill
Interrogating requirements to validate before building. Use before swarm decomposition, design decisions on ambiguous features, or when scope creep risk is high.
team
Referencing the agent roster, roles, coordination model, and dispatch modes. Use when spawning agents or checking permissions.
ticket
Associate every PDS task with a GitHub issue. Orchestrator finds or creates the ticket, posts plan and acceptance criteria as a checkbox list, updates it as work progresses. Use at Phase 1 of every swarm.
triage
Triage insights into actionable GitHub issues across repos. Use after running /insights to convert analysis into tracked work.