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/setup)<a href="https://agentmods.dev/commands/vsladkov/claudex-stereo/setup"><img src="https://agentmods.dev/badge/commands/vsladkov/claudex-stereo/setup/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/setup"><img src="https://agentmods.dev/badge/commands/vsladkov/claudex-stereo/setup.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.00019 | $0.00678 |
| Opus 5.5 | $0.00008 | $0.00271 |
| Sonnet 5.5 | $0.00004 | $0.00136 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
setup 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
Happy path:
- Install the Stereo plugin.
- When the report's
- auth:line is not ready, run!codex login; use!codex login --device-author!codex login --with-api-keywhen the report names those fallbacks. - When the
- claude:or- claude auth:line is not ready, follow its next step: install or update Claude Code to the version the report names, or runclaude auth login. - Configure optional third-party provider keys only when the report lists unconfigured aliases or missing provider environment variables.
- Optionally run
/stereo:setup --enable-review-gatewhen- review gate:is disabled. - Optionally run
/stereo:configto set workspace role defaults when- role defaults:says none are configured. - Verify the workspace with
/stereo:statusafter the- codex:,- auth:,- claude:, and- claude auth:checks are ready.
Use /stereo:doctor when install readiness is healthy but workspace runtime or durable state needs
inspection.
Raw slash-command arguments:
$ARGUMENTS
Parse them before running anything: the only accepted flags are --enable-review-gate and
--disable-review-gate, at most one of them. Reject any other token, and both flags together,
naming the two accepted flags. <setupFlags> is the accepted flag as its own argument, or nothing;
never pass the raw arguments through the shell. Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.ts" setup --json <setupFlags>
If the payload's codex.available is false and npm.available is true:
- Use
AskUserQuestionexactly once to ask whether Claude should install Codex now. - Put the install option first and suffix it with
(Recommended). - Use these two options:
Install Codex (Recommended)Skip for now
- If the user chooses install, run:
npm install -g @openai/codex
- Then rerun:
node "${CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.ts" setup --json <setupFlags>
If Codex is already installed or npm is unavailable:
- Do not ask about installation.
Output rules:
- Print the payload's
renderedfield verbatim — the complete# Stereo Setupreport — and relay its next steps as written, including every exact path, environment-variable name, and!codex loginfallback. Never reconstruct, paraphrase, or reorder it. - If installation was skipped, print the original run's
renderedreport.
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 · +6 lines · +2 tokens per session e0a74f48af32
- 1mo ago First seen · 62 lines · 17 tokens per session scan A 1d4374c8bfb9
setup is a command published in the GitHub repository vsladkov/claudex-stereo (4 stars, last pushed 21d ago), licensed Apache-2.0. It adds 19 tokens to every session and 678 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.