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/presetgit 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/preset)<a href="https://agentmods.dev/commands/xiaoliu10/claude-code-router-next/preset"><img src="https://agentmods.dev/badge/commands/xiaoliu10/claude-code-router-next/preset.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.1 | $0.00000 | $0.01363 |
| Opus 5 | $0.00000 | $0.00681 |
| Sonnet 5 | $0.00000 | $0.00273 |
| Haiku 4.5 | $0.00000 | $0.00136 |
Grade A, and why
preset 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ccr preset
Manage presets - configuration templates that can be shared and reused.
Overview
Presets allow you to:
- Save your current configuration as a reusable template
- Share configurations with others
- Install pre-configured setups from the community
- Switch between different configurations easily
Commands
export
Export your current configuration as a preset.
ccr preset export <name> [options]
Options:
--output <path>- Custom output directory path--description <text>- Preset description--author <name>- Preset author--tags <tags>- Comma-separated keywords--include-sensitive- Include API keys and sensitive data (not recommended)
Example:
ccr preset export my-config --description "My production setup" --author "Your Name"
What happens:
- Reads current configuration from
~/.claude-code-router/config.json - Prompts for description, author, and keywords (if not provided)
- Sanitizes sensitive fields (API keys become placeholders)
- Creates preset directory at
~/.claude-code-router/presets/<name>/ - Generates
manifest.jsonwith configuration and metadata
install
Install a preset from a local directory.
ccr preset install <source>
Sources:
- Local directory path:
/path/to/preset-directory - Preset name (for reconfiguring an already installed preset):
preset-name
Example:
# Install from directory
ccr preset install ./my-preset
# Reconfigure an installed preset
ccr preset install my-preset
What happens:
- Reads
manifest.jsonfrom the preset directory - Validates the preset structure
- If the preset has a
schema, prompts for required values (API keys, etc.) - Copies preset to
~/.claude-code-router/presets/<name>/ - Saves user inputs in
manifest.json
Note: URL installation is not currently supported. Download the preset directory first.
list
List all installed presets.
ccr preset list
Example output:
Available presets:
• my-config (v1.0.0)
My production setup
by Your Name
• openai-setup
Basic OpenAI configuration
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.
- 5d ago First seen · 255 lines · 0 tokens per session scan A fc2fd46a5eb2
preset is a command published in the GitHub repository xiaoliu10/claude-code-router-next (11 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,363 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-propose
Propose a new change - create it and generate all artifacts in one step.
/opsx-ff
Create a change and generate all artifacts needed for implementation in one go.
/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.