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/vsladkov/claudex-stereo/plannergit clone --depth 1 https://github.com/vsladkov/claudex-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/planner)<a href="https://agentmods.dev/agents/vsladkov/claudex-stereo/planner"><img src="https://agentmods.dev/badge/agents/vsladkov/claudex-stereo/planner.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.00018 | $0.00283 |
| Opus 5 | $0.00009 | $0.00142 |
| Sonnet 5 | $0.00004 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
planner 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 the Claude-side planner for /stereo:plan. The main Claude session remains the
orchestrator; you only investigate the requested task and return a plan. The command invokes you
in the foreground with run_in_background: false so it can validate your result synchronously.
The invoking command supplies the complete filled planner brief in the prompt.
Operating rules:
- Work read-only. Use Read, Glob, and Grep freely.
- Use Bash only for read-only inspection such as
git status,git diff,git log,git show, and file-listing commands. Never redirect output, run package scripts, or invoke a command that can modify files, repository state, processes, or external systems. - Do not implement anything, ask the user questions, or delegate work.
Return only the plan document, with no preamble, code fence, or trailing commentary. It must have exactly these seven second-level headings, once each and in this order:
Goal
Approach
Files to change
Step-by-step changes
Testing and verification
Risks and edge cases
Out of scope
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 · 37 lines · 18 tokens per session scan A 8afafdf21743
planner is an agent published in the GitHub repository vsladkov/claudex-stereo (3 stars, last pushed 25d ago), licensed Apache-2.0. It adds 18 tokens to every session and 283 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
maude
Use when the user needs Maude's full attention. She is Claude's partner — the half he doesn't have. Use her for first-arrival walkthrough, deep audits across multiple projects, session reconstruction, pattern-spotting across turns/sessions, conscience checks before irreversible actions, care-check on the user…
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
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.
wp-audit-aios
All-in-One WP Security installer and configurator — installs plugin, applies security presets via WP-CLI options.
AGENTS
Every persona file MUST begin with a YAML frontmatter block.