mux-status

mux-status is a command for Claude Code from wowoyong/agent-mux. It costs 15 tokens per session (436 once invoked), scanned A, original, MIT.

A status command that displays the agent-mux budget, task counts, session details, installed plugins, and tool availability in a dashboard.

In plain words
What is it for?
Use `/mux-status` to check Claude and Codex usage, success rates, escalations, detected plugins, and whether Codex CLI is installed.
Why use it?
It puts usage and system information in one place so you can see remaining capacity and possible warnings.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Codex.

Part of the agent-mux plugin — 1 skill, 4 commands, 4 agents, 1 hook shipped together

Good fit Use /mux-status to check Claude and Codex usage, success rates, escalations, detected plugins, and whether Codex CLI is installed.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/wowoyong/agent-mux/mux-status
Install

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.

Clone the repo
git clone --depth 1 https://github.com/wowoyong/agent-mux

Made for: Claude Code.

Or install agent-mux, the plugin that ships this one along with the rest of its 1 skill, 4 commands, 4 agents, 1 hook.

Wrote 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.

agentmods badge for mux-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/wowoyong/agent-mux/mux-status/github.svg)](https://agentmods.dev/commands/wowoyong/agent-mux/mux-status)
Your own site
<a href="https://agentmods.dev/commands/wowoyong/agent-mux/mux-status"><img src="https://agentmods.dev/badge/commands/wowoyong/agent-mux/mux-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.

agentmods 80×15 button for mux-status

Your own site · 80×15
<a href="https://agentmods.dev/commands/wowoyong/agent-mux/mux-status"><img src="https://agentmods.dev/badge/commands/wowoyong/agent-mux/mux-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 436 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.00436
Opus 5 $0.00008 $0.00218
Sonnet 5 $0.00003 $0.00087
Haiku 4.5 $0.00002 $0.00044

Measured 8d ago against content hash 8cb26f97d462, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

mux-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 8d 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.

commands/mux-status.md · 52 lines

What it actually says

/mux-status

Call the get_mux_status MCP tool and display results as a formatted dashboard.

Display Format

Show this dashboard format to the user:

[agent-mux] ═══ Agent Mux Status ═══

  Tier: {tier} ({claude_plan} + {codex_plan})
  Session: {session_duration} elapsed

  ┌─ Budget ─────────────────────────────────┐
  │ Claude:  {progress_bar}  {used}/{total}  │
  │ Codex:   {progress_bar}  {used}/{total}  │
  └──────────────────────────────────────────┘

  Session Stats:
  ├─ Total tasks: {total}
  ├─ Claude: {claude_count} tasks
  ├─ Codex: {codex_count} tasks ({success_rate}% success)
  └─ Escalations: {escalation_count}

  Warnings: {warnings_list or "none"}

  Detected Plugins: {plugin_list or "none"}
  Codex CLI: {version or "not installed"}

Progress Bar Format

Use block characters to create a visual progress bar:

  • Under 50%: ████░░░░░░░░░░░░░░░░ (green feeling)
  • 50-74%: ████████████░░░░░░░░ (normal)
  • 75-89%: ██████████████████░░ ⚠️ (warning)
  • 90%+: ████████████████████ 🚨 (critical)

Budget Tier-Specific Behavior

  • Budget ($40): Show "CONSERVE" label if >50% used
  • Standard ($120): Normal display
  • Premium ($220): Minimal warnings
  • Power ($400): Relaxed display

If there are active warnings, display them prominently below the budget section.

Changes

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.

  1. 8d ago First seen · 52 lines · 15 tokens per session scan A 8cb26f97d462

Subscribe to this mod's changes

mux-status is a command published in the GitHub repository wowoyong/agent-mux (1 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 436 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.