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/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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/vsladkov/claudex-stereo/status"><img src="https://agentmods.dev/badge/commands/vsladkov/claudex-stereo/status.svg" alt="Reviewed on agentmods" width="80" 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.00015 | $0.00508 |
| Opus 5.5 | $0.00006 | $0.00203 |
| Sonnet 5.5 | $0.00003 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
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 21d 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 --args-stdin <<'STEREO_ARGS_Q7X2'
$ARGUMENTS
STEREO_ARGS_Q7X2
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. --all lists every session's jobs in this workspace, not only this
session's, and lifts the cap on recent finished jobs.
--brief with a job ID prints one line, <status> <phase> <elapsedSeconds>s; present it verbatim.
A stalled phase means the job's worker process is gone, so no wait will settle it: point to
/stereo:cancel <id>.
When the user passed --usage, present the # Stereo 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 or Claude account usage or
all-time history.
If the user did not pass a job ID, present the command output as printed: the # Stereo Status
heading, the Session runtime: and Review gate: lines, the active-jobs table with its Model
column, the latest finished job, and the other recent jobs. Add no field the output omits and no
commentary of your own. --verbose adds per-job detail lines for log paths, timestamps, and
progress; present those as printed too.
If the user did pass a job ID:
- Present the full
# Stereo Job Statusoutput to the user. - Do not summarize or condense it; preserve its
Model:, session-id, and resume lines verbatim.
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.
- 21d ago Changed · +3 lines · -1 tokens per session fe865d1ca3a0
- 1mo ago First seen · 37 lines · 16 tokens per session scan A 0a23e2a1c957
status is a command published in the GitHub repository vsladkov/claudex-stereo (4 stars, last pushed 21d ago), licensed Apache-2.0. It adds 15 tokens to every session and 508 once invoked, about $0.0001 per session on Opus 5.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
check
Quick sanity check - code (inline 6-perspective) or plan (--plan).
end
End a work session - a settlement pass that reconciles uncommitted / unpushed work + session context into git, the tracker, and a session snapshot file. --session (aliases --snapshot, --pre-compact, --compact) skips settlement and only writes the shared snapshot, keeping the session going.
note
Add a note to the active task - progress, decisions, context. --session (aliases --snapshot, --pre-compact, --compact) writes a resume-grade session snapshot without ending the session. --team writes a fact or a decision into the standing team's file.
review-round
Work through a RECEIVED round of review comments (inline markers, a review file, or PR threads) on a spec/doc/PR. Triage each item, record decisions to the tracker task, keep the artifact FROZEN, then apply all edits in ONE final pass. Use when a reviewer returns N comments to incorporate.
hub
Cross-project hub on Orca - see every project's orchestrators, ask a stopped one read-only, wake one for gated work (Orca addon).
statusline
Manage & persist statusline appearance - light/dark, compact, and which rows to show.