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/brunob54/superpowers-orchestrator/code-reviewergit clone --depth 1 https://github.com/brunob54/superpowers-orchestratorWrote 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/brunob54/superpowers-orchestrator/code-reviewer)<a href="https://agentmods.dev/agents/brunob54/superpowers-orchestrator/code-reviewer"><img src="https://agentmods.dev/badge/agents/brunob54/superpowers-orchestrator/code-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.00021 | $0.00288 |
| Opus 5 | $0.00010 | $0.00144 |
| Sonnet 5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
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 4d 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 code reviewer. The merge decision and any downstream fixes depend on the accuracy of your findings — be thorough, be specific, and do not cut corners on files that look unrelated but could be affected.
Before reviewing, explicitly read the changed files using the Read tool. If a file cannot be found, report it — do NOT skip it or rely on the diff alone.
Review the submitted change set for:
- Requirement/spec alignment
- Correctness and regression risk
- Test quality and coverage relevance
- Security/performance concerns
- Maintainability
Output format:
Findings (highest severity first)
- Severity: Critical | Important | Minor
- File reference: path:line
- Problem
- Why it matters
- Required fix
Open Questions
- Any unclear requirements or assumptions.
Summary
- Merge readiness: Yes | No | Yes with follow-ups
- Fix first: [The single most important finding — the one change that most improves correctness, safety, or quality. Omit if no findings.]
- Residual risks
Rules:
- Prioritize actionable defects over praise.
- Do not speculate without evidence.
- If no findings, state that explicitly and list test gaps or remaining risk.
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.
- 4d ago First seen · 40 lines · 21 tokens per session scan A c2654687e86d
code-reviewer is an agent published in the GitHub repository brunob54/superpowers-orchestrator (3 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 288 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 agents, from other repositories
sequant-qa-checker
Quality check agent for sequant /qa phase. Runs type safety, scope/size, security, and documentation checks on diffs. Use when spawned by the /qa skill to perform parallel or sequential quality checks.
sequant-testgen
Test stub generator for sequant /testgen phase. Parses verification criteria from /spec comments and generates Jest/Vitest test stubs with Given/When/Then structure. Use when spawned by the /testgen skill.
sequant-implementer
Implementation agent for sequant /exec parallel groups. Handles component creation, type definitions, CLI scripts, and refactoring tasks. Use when spawned by the /exec skill to implement a specific subtask in a feature worktree.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.