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/statusgit 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/status)<a href="https://agentmods.dev/commands/vsladkov/claudex-stereo/status"><img src="https://agentmods.dev/badge/commands/vsladkov/claudex-stereo/status.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.00016 | $0.00497 |
| Opus 5 | $0.00008 | $0.00249 |
| Sonnet 5 | $0.00003 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
status 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" status "$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.
When the user passed --usage, present the usage headline and both tables verbatim. Preserve the
window and scope sentence exactly, including whether it covers this session or the workspace.
Never describe these local retained-job totals as Codex account usage or all-time history.
If the user did not pass a job ID:
- When the user passed
--verbose, do not compress the command output to the single compact table; include its per-job detail lines for log paths, timestamps, and progress. - When the user did not pass
--verbose, render the command output as a single Markdown table for the current and past runs in this session. - Keep non-verbose output compact. Preserve the
Session runtime:andReview gate:header lines above the table, but do not include progress blocks or other prose outside the table except for aWarnings:section from the command output. - Preserve the actionable fields the command output actually contains. Active jobs and the latest finished job carry job ID, kind, model, status, phase, elapsed or duration, summary, and follow-up commands; other recent jobs render as one line (id, status, kind, title, duration) — present that line as-is and never invent the fields it omits.
- Keep the
Modelcolumn in the active-jobs table; it may showmodel@provider, and an absent model must remain-.
If the user did pass a job ID:
- Present the full command output to the user.
- Do not summarize or condense it.
Always preserve any Warnings: section and its file paths verbatim in both table and per-job presentations.
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 · 16 tokens per session scan A 0a23e2a1c957
status is a command published in the GitHub repository vsladkov/claudex-stereo (3 stars, last pushed 26d ago), licensed Apache-2.0. It adds 16 tokens to every session and 497 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.
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.
teach
Tell Maude something about yourself directly — how you work, your rhythm, what help you want — and she records it in her cross-project profile of you. Use when you want her to KNOW a fact rather than wait for her to infer it. Tier 0, user-global, no network.
verify
Run Maude's programmatic project audit — version consistency, JSON validity, link integrity, header dates, watch-list paths, worn-framing scan. Catches "ready" before it's actually ready.