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 commands/vsladkov/claudex-stereo/resultgit 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/commands/vsladkov/claudex-stereo/result)<a href="https://agentmods.dev/commands/vsladkov/claudex-stereo/result"><img src="https://agentmods.dev/badge/commands/vsladkov/claudex-stereo/result.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.00014 | $0.00290 |
| Opus 5 | $0.00007 | $0.00145 |
| Sonnet 5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
result 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
!node "${CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.ts" result "$ARGUMENTS"
Use --workspace <path> to inspect jobs recorded against another repository root, such as the
main workspace used by a worktree-isolated /stereo:implement --isolated or
/stereo:tournament run.
Present the full command output to the user. Do not summarize or condense it. Preserve all details including:
- Job ID and status
- The complete result payload, including verdict, summary, findings, details, artifacts, and next steps
- File paths and line numbers exactly as reported
- Any error messages or parse errors
- Any
Warnings:section and its file paths verbatim - Follow-up commands such as
/stereo:status <id>and/stereo:review - Following
codex-result-handling, keep review findings in severity order with their evidence boundaries intact. codex-result-handlingCRITICAL: After presenting review findings, stop. Never apply or offer to apply a fix; ask the user which issues to fix before touching a file.
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 · 26 lines · 14 tokens per session scan A 74b26b5a4d81
result is a command published in the GitHub repository vsladkov/claudex-stereo (3 stars, last pushed 26d ago), licensed Apache-2.0. It adds 14 tokens to every session and 290 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 commands, from other repositories
rest
Maude's end-of-session ritual — digest + tomorrow's starting point + close-the-loop check + full save fan-out. Run before you stop, so the next session opens cleanly. Session-end is the right time to pay network cost, so Tier 2 writes happen here when registered.
save
Save the current session digest. Fans out across every writable memory tier per the house-map. Tier 0 always; Tier 1 if reachable; Tier 2 only if registered writable with auth. Each tier independent — failures degrade gracefully.
wake
Maude's session-start ritual — brief + house-walk + 1-3 things to know first. Runs at session-start manually if SessionStart hook didn't catch you, or anytime you need a clean re-orient. Cheap by design — Tier 0 always, Tier 1 if cached-up, Tier 2 never.
freshen
Re-check the vault's live-state claims against the world. Walks now memory files for verify lines, runs each read-only command, reports CONFIRMED / STALE / CHECK-FAILED / UNVERIFIABLE. Report-first — never edits memory.
notice
Maude surfaces patterns from the turn-by-turn trace — recurring topics, repeated mistakes, time-of-day patterns, sessions that keep ending in the same place.
promote
Show what the tape is holding for your word, and promote the ones you approve into canon. Agent inference never becomes canon on its own — this is the door, and your hand is on it.