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 skills add sepehrbayat/SEPCC --skill claude-command-routergit clone --depth 1 https://github.com/sepehrbayat/SEPCCWrote 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/skills/sepehrbayat/sepcc/claude-command-router)<a href="https://agentmods.dev/skills/sepehrbayat/sepcc/claude-command-router"><img src="https://agentmods.dev/badge/skills/sepehrbayat/sepcc/claude-command-router/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/skills/sepehrbayat/sepcc/claude-command-router"><img src="https://agentmods.dev/badge/skills/sepehrbayat/sepcc/claude-command-router.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.00020 | $0.00365 |
| Opus 5 | $0.00010 | $0.00182 |
| Sonnet 5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
claude-command-router 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 10d 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
Claude Command Router
Use this skill when a user asks which Claude Code command to run, when a task looks like a known Claude Code workflow, or when you are about to add FCC-specific orchestration.
Protocol
Prefer Claude Code built-ins when they already fit:
- Project onboarding: suggest
/initto create or refreshCLAUDE.md; usefcc-bootstrap-contextonly for FCC hooks, handoff files, subagents, and retrieval policy. - Context pressure: suggest
/context allto inspect usage, then/compact <focus>when the session should continue with less history. - Diff review: suggest
/difffor inspection,/code-reviewfor correctness, and/security-reviewfor security-specific risk. - Large codebase changes: suggest
/batchwhen independent worktree units make sense; otherwise plan in the main session and use FCC subagents only for bounded research or review. - Runtime problems: suggest
/doctor,/debug,/status, orfcc context doctordepending on whether the problem is Claude Code, provider/proxy, or FCC scaffold. - App verification: suggest
/runor/verifywhen a user-facing app change needs live validation. - Interface ergonomics: suggest
/config,/theme,/statusline,/terminal-setup, or/tui fullscreen.
Do not rewrite an explicit slash command. Let commands such as /init, /compact, and /context all pass through unchanged.
If no built-in command fits, continue with the normal FCC workflow: use project context, subagents only when they reduce risk or noise, and run the repository checks before finalizing code 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.
- 10d ago First seen · 25 lines · 20 tokens per session scan A c9e6a643f602
claude-command-router is a skill published in the GitHub repository sepehrbayat/SEPCC (39 stars, last pushed 18d ago), licensed MIT. It adds 20 tokens to every session and 365 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-30.
Other skills, from other repositories
memory
Persistent global memory across conversations. Read memory file at start of every conversation, write important context during conversation so it survives context compression. Use ALWAYS. Triggered automatically.
token-saver
Minimize token consumption & maximize prompt cache hit rate. Use when user asks to save tokens, reduce cost, improve cache hit rate, or be more concise.
editing-cordis-compositions
Use when creating, changing, or validating a Cordis composition for this harness — writing or editing an agent preset, adding or removing a plugin row, deciding whether something belongs to the host composition or to one session, checking whether a preset you authored actually mounts, or diagnosing a row that mounted…
cordis-plugin-development
Create, modify, debug, or extend dynamic Cordis Plugins, including Host Services and Events, Client Slot and theme UI, Package-private Client-to-Host calls, dynamic Tools, version updates, approval failures, and runtime diagnostics. Use this Skill to route a user request to the correct platform and Inspect Provider…
weibo-poster
A writing guide for Weibo, a Chinese microblogging platform similar to a short-post social network. It covers concise posts, longer posts, hashtags, @ mentions, image layouts, and posting-time suggestions.
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.