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/startgit 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/start)<a href="https://agentmods.dev/commands/xiaoliu10/claude-code-router-next/start"><img src="https://agentmods.dev/badge/commands/xiaoliu10/claude-code-router-next/start.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.00441 |
| Opus 5 | $0.00000 | $0.00220 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
start 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 3d 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 start
Start the Claude Code Router server.
Usage
ccr start [options]
Options
| Option | Alias | Description |
|---|---|---|
--port <number> |
-p |
Port to listen on (default: 8080) |
--config <path> |
-c |
Path to configuration file |
--daemon |
-d |
Run as daemon (background process) |
--log-level <level> |
-l |
Log level (fatal/error/warn/info/debug/trace) |
Examples
Start with default settings
ccr start
Start on custom port
ccr start --port 3000
Start with custom config
ccr start --config /path/to/config.json
Start as daemon
ccr start --daemon
Start with debug logging
ccr start --log-level debug
Environment Variables
You can also configure the server using environment variables:
| Variable | Description |
|---|---|
PORT |
Port to listen on |
CONFIG_PATH |
Path to configuration file |
LOG_LEVEL |
Logging level |
CUSTOM_ROUTER_PATH |
Path to custom router function |
HOST |
Host to bind to (default: 0.0.0.0) |
Output
When started successfully, you'll see:
Claude Code Router is running on http://localhost:8080
API endpoint: http://localhost:8080/v1
Related Commands
- ccr stop - Stop the server
- ccr restart - Restart the server
- ccr status - Check server status
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.
- 3d ago First seen · 82 lines · 0 tokens per session scan A 3a2a86f31f4f
start 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 441 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.