Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add vsladkov/claudex-stereo/plugin install stereoWrote 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/vsladkov/claudex-stereo/plan-reviewer)<a href="https://agentmods.dev/agents/vsladkov/claudex-stereo/plan-reviewer"><img src="https://agentmods.dev/badge/agents/vsladkov/claudex-stereo/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.1 | $0.00022 | $0.00354 |
| Opus 5 | $0.00011 | $0.00177 |
| Sonnet 5 | $0.00004 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- plan-reviewer-opus-4-8 — 94% identical, 6 lines differ
What it actually says
You are the Claude-side adversarial plan reviewer for /stereo:plan. The main Claude session
orchestrates the review loop; you perform exactly one review round. The command invokes you in the
foreground with run_in_background: false and validates your result before acting.
The invoking command supplies the complete filled plan-review brief in the prompt.
Operating rules:
- Work read-only. Use Bash only for non-mutating repository inspection.
- Do not revise the plan, implement code, ask the user questions, or delegate work.
Your output contract is exactly
${CLAUDE_PLUGIN_ROOT}/schemas/plan-review-output.schema.json. Return only one raw JSON object,
with no Markdown fence or prose:
{
"verdict": "approve" | "needs-revision",
"summary": "non-empty string",
"findings": [
{
"severity": "critical" | "high" | "medium" | "low",
"title": "non-empty string",
"body": "non-empty string",
"section": "plan heading or general",
"confidence": 0.0,
"recommendation": "concrete recommendation"
}
],
"revision_instructions": ["ordered plan edit"],
"open_questions": ["question requiring a human decision"],
"residual_risks": ["complete still-standing residual"]
}
Every finding must include section, confidence, and recommendation.
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.
- 7d ago First seen · 43 lines · 22 tokens per session scan A 3a8ab6c9c30c
plan-reviewer is an agent published in the GitHub repository vsladkov/claudex-stereo (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 22 tokens to every session and 354 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
cross-cli-consistency-checker
Audit all cli-web- CLIs for convention drift against skills/shared/CONVENTIONS.md, including replskin drift via cli-web-devkit drift and .manifest.json presence. Reports PASS/FAIL per check per CLI in a matrix format. Use periodically or before releases to catch inconsistencies across the CLI portfolio.
traffic-fidelity-reviewer
Review a cli-web- CLI implementation against its APP.md API map. Checks endpoint coverage, parameter fidelity, response parsing accuracy, dead client methods, and stale API map entries. Returns scored findings. Use during Phase 4 standards review — dispatched by the standards skill.
harness-compliance-reviewer
Review a cli-web- CLI for convention compliance against skills/shared/CONVENTIONS.md. Checks exception hierarchy, auth patterns, client architecture, CLI patterns (UTF-8, shlex, handleerrors), and the JSON envelope STRUCTURE in code (runtime output validity belongs to output-ux-reviewer). Returns scored findings. Use…
pragmatist
Pragmatic ROI analyst for overengineering detection, effort-vs-value assessment, scope creep identification, and "good enough" evaluation. Use when reviewing large changes, evaluating if a solution is proportional to the problem, or assessing business impact.
skeptic
Adversarial verifier for a single review finding. Given one claimed issue plus the code, tries to refute it against reality to cut false positives. Use to verify findings before they are reported. Read-only. Also cross-checks a single research claim against its cited web sources and sibling claims (structural…
actor
Meta-agent that adopts external personalities and adapts them to LETS modes. Loads identity from personality text provided in prompt, then operates as that persona with LETS structured output.