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/xiaoliu10/claude-code-router-next/statusgit clone --depth 1 https://github.com/xiaoliu10/claude-code-router-nextWrote 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/xiaoliu10/claude-code-router-next/status)<a href="https://agentmods.dev/commands/xiaoliu10/claude-code-router-next/status"><img src="https://agentmods.dev/badge/commands/xiaoliu10/claude-code-router-next/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.00000 | $0.00287 |
| Opus 5 | $0.00000 | $0.00143 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00029 |
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
ccr status
Show the current status of the Claude Code Router server.
Usage
ccr status
Output
Running Server
When the server is running:
Claude Code Router Status: Running
Version: 2.0.0
PID: 12345
Port: 8080
Uptime: 2h 34m
Configuration: /home/user/.claude-code-router/config.json
Stopped Server
When the server is not running:
Claude Code Router Status: Stopped
Exit Codes
| Code | Description |
|---|---|
| 0 | Server is running |
| 1 | Server is stopped |
| 2 | Error checking status |
Examples
$ ccr status
Claude Code Router Status: Running
Version: 2.0.0
PID: 12345
Port: 8080
Uptime: 2h 34m
Related Commands
- ccr start - Start the server
- ccr stop - Stop the server
- ccr restart - Restart the server
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 · 63 lines · 0 tokens per session scan A bcc17a8e515a
status is a command published in the GitHub repository xiaoliu10/claude-code-router-next (11 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 287 tokens. 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-30.
Other commands, from other repositories
/opsx-ff
Create a change and generate all artifacts needed for implementation in one go.
/opsx-propose
Propose a new change - create it and generate all artifacts in one step.
/opsx-archive
Archive a completed change in the experimental workflow.
/opsx-explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
/opsx-continue
Continue working on a change - create the next artifact (Experimental).
/opsx-sync
Sync delta specs from a change to main specs.