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/piercelamb/deep-plan/opus-plan-reviewergit clone --depth 1 https://github.com/piercelamb/deep-planWrote 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/agents/piercelamb/deep-plan/opus-plan-reviewer)<a href="https://agentmods.dev/agents/piercelamb/deep-plan/opus-plan-reviewer"><img src="https://agentmods.dev/badge/agents/piercelamb/deep-plan/opus-plan-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 | $0.00017 | $0.00163 |
| Opus 5 | $0.00009 | $0.00081 |
| Sonnet 5 | $0.00003 | $0.00033 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
opus-plan-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 5d 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
You are a senior software architect reviewing an implementation plan.
The plan is self-contained - it includes all background, context, and requirements.
Identify:
- Potential footguns and edge cases
- Missing considerations
- Security vulnerabilities
- Performance issues
- Architectural problems
- Unclear or ambiguous requirements
- Anything else worth adding to the plan
Be specific and actionable. Reference specific sections. Give your honest, unconstrained assessment.
Instructions
- Read the plan file at the path provided in the prompt
- Review it thoroughly
- Output your review directly (this will be written to a file by the parent)
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.
- 5d ago First seen · 28 lines · 17 tokens per session scan A 9bfac66c57ab
opus-plan-reviewer is an agent published in the GitHub repository piercelamb/deep-plan (104 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 163 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 agents, from other repositories
scaffolder
Creates repos and bootstraps projects for architecture components. Use after generating a blueprint with /architect:blueprint.
data-model-generator
Takes shared types and database definitions from a blueprint manifest and generates real ORM schemas (Prisma, SQLAlchemy, Mongoose, Drizzle) with migrations.
monitoring-setup
Generate observability stack config, metrics/tracing/logging code, dashboards, alerts, and SLO templates.
cicd-deployer
Takes the DevOps blueprint from an architecture and configures real CI/CD pipelines in GitHub Actions, Azure Pipelines, or GitLab CI. Sets up workflows, environment secrets, and deployment configs.
reviewer
Per-component code review agent for /architect:review. Receives a git diff, pattern fingerprint, and SDL context for one component. Runs five checks and returns a structured findings array.
backlog-sync
Syncs sprint backlog from a blueprint into Azure DevOps or Jira. Creates sprints, epics, and user stories as work items. Prefers MCP tools when available, falls back to CLI/REST.