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/plan-state)<a href="https://agentmods.dev/commands/vsladkov/claudex-stereo/plan-state"><img src="https://agentmods.dev/badge/commands/vsladkov/claudex-stereo/plan-state/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/plan-state"><img src="https://agentmods.dev/badge/commands/vsladkov/claudex-stereo/plan-state.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.00023 | $0.00990 |
| Opus 5.5 | $0.00009 | $0.00396 |
| Sonnet 5.5 | $0.00005 | $0.00198 |
| Haiku 4.5 | $0.00002 | $0.00099 |
Grade A, and why
plan-state 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" plan-state --metadata
Raw slash-command arguments:
$ARGUMENTS
The preamble shows the default slot's metadata only, so a flagged invocation never pays for a
plan document it will not use. With no arguments, run
node "${CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.ts" plan-state and present that full output
(metadata plus the stored plan document) instead of the preamble. With --list, --compare, or
an explicit --slot,
run the requested companion command and present that output instead.
Apply at most one action. Compose every command below from the parsed flags, each slot name its own
single-quoted argument (an embedded ' written as '"'"'; the companion rejects such a name
anyway), and never pass $ARGUMENTS itself through the shell:
- With
--list, runnode "${CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.ts" plan-state --listand present the slot inventory verbatim.--listdoes not combine with--slot. - With
--compare <slotA> <slotB>, runnode "${CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.ts" plan-state --compare '<slotA>' '<slotB>'and present the comparison verbatim: both metadata blocks and the plan diff.--comparenames both slots, so it does not combine with--slotor another action. Both slots must hold a stored plan; on a missing-slot error, relay the message and point the user at/stereo:plan-state --list. When the diff is suppressed, relay the export hint instead of attempting a diff yourself. - With
--open, runnode "${CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.ts" plan-state --open [--slot '<slot>']and relay the exported path and whether VS Code opened. - With
--clearand an explicit slot, first runnode "${CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.ts" plan-state --metadata --json --slot '<slot>'and use its summary, verdict, round, andupdatedAtto describe that exact slot in the confirmation. Then useAskUserQuestionexactly once withDelete the plan in slot <slot>andKeep it (Recommended). Without an explicit slot, ask withDelete the stored plan and any implementation recordandKeep it (Recommended). Runnode "${CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.ts" plan-state --clear [--slot '<slot>']only when deletion is confirmed. - With
--mark-implemented, runnode "${CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.ts" plan-state --mark-implemented [--slot '<slot>']and note that this marker is normally set automatically by/stereo:implementafter a successful full phase. - With an explicit
--slotand no action, runnode "${CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.ts" plan-state --slot '<slot>'.
Present the full command output to the user. Do not summarize or condense it.
When the output includes the stored plan document (the no-argument and --slot reads), render
it as Markdown while preserving its contents verbatim; action outputs (--list, --clear,
--mark-implemented, --metadata) contain no plan document — do not fetch one to show.
Clearing a slot removes the implementation record only when that record belongs to the cleared
slot. When --clear also removes an implementation record, preserve the extra status and path
lines. Relay the Kept the implementation record... line verbatim when it is present.
Relay implementedAt when present; it means a full implementation phase completed with an
accepted review, not that the work was committed or merged.
If no plan is stored, relay the message and point the user to /stereo:plan.
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 · +2 lines 406f46b2dba0
- 1mo ago First seen · 60 lines · 23 tokens per session scan A 3c5642e75ad9
plan-state is a command published in the GitHub repository vsladkov/claudex-stereo (4 stars, last pushed 21d ago), licensed Apache-2.0. It adds 23 tokens to every session and 990 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.