router-stats
Display Claude Router usage statistics and cost savings
Best use case
router-stats is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Display Claude Router usage statistics and cost savings
Display Claude Router usage statistics and cost savings
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "router-stats" skill to help with this workflow task. Context: Display Claude Router usage statistics and cost savings
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/router-stats/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How router-stats Compares
| Feature / Agent | router-stats | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Display Claude Router usage statistics and cost savings
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Router Stats
Display usage statistics and estimated cost savings from Claude Router.
## Instructions
Read the stats file at `~/.claude/router-stats.json` and present the data in a clear, formatted way.
## Data Format
The stats file contains (v1.2 schema):
```json
{
"version": "1.2",
"total_queries": 100,
"routes": {"fast": 30, "standard": 50, "deep": 10, "orchestrated": 10},
"exceptions": {"router_meta": 15, "slash_commands": 0},
"tool_intensive_queries": 25,
"orchestrated_queries": 10,
"estimated_savings": 12.50,
"delegation_savings": 2.50,
"sessions": [
{
"date": "2026-01-03",
"queries": 25,
"routes": {"fast": 8, "standard": 12, "deep": 2, "orchestrated": 3},
"savings": 3.20
}
],
"last_updated": "2026-01-03T15:30:00"
}
```
## Output Format
Present the stats like this:
```
╔═══════════════════════════════════════════════════╗
║ Claude Router Statistics ║
╚═══════════════════════════════════════════════════╝
📊 All Time
───────────────────────────────────────────────────
Total Queries Routed: 100
Route Distribution:
Fast (Haiku): 30 (30%) ████████░░░░░░░░░░░░
Standard (Sonnet): 50 (50%) ██████████████░░░░░░
Deep (Opus): 10 (10%) ████░░░░░░░░░░░░░░░░
Orchestrated: 10 (10%) ████░░░░░░░░░░░░░░░░
🔧 Tool-Aware Routing
───────────────────────────────────────────────────
Tool-Intensive Queries: 25 (25%)
Orchestrated Queries: 10 (10%)
⚡ Exceptions (handled by Opus despite classification)
───────────────────────────────────────────────────
Router Meta-Queries: 15 (queries about the router itself)
Total Exceptions: 15
💰 Cost Savings
───────────────────────────────────────────────────
Estimated Savings: $12.50 (compared to always using Opus)
Delegation Savings: $2.50 (from hybrid delegation)
Total Savings: $15.00
📅 Today (2026-01-03)
───────────────────────────────────────────────────
Queries: 25
Savings: $3.20
Route Distribution:
Fast: 8 | Standard: 12 | Deep: 2 | Orchestrated: 3
```
## Steps
1. Use the Read tool to read `~/.claude/router-stats.json`
2. If the file doesn't exist, inform the user that no stats are available yet
3. Calculate percentages for route distribution
4. Display exception counts if present (router_meta queries are handled by Opus despite classification)
5. Format and display the statistics
6. Include the savings comparison explanation
## Notes
- Savings are calculated assuming Opus would have been used for all queries
- Cost estimates use: Haiku 4.5 $1/$5, Sonnet 4.5 $3/$15, Opus 4.5 $5/$25 per 1M tokens
- Average query estimated at 1K input + 2K output tokens
- **Exceptions**: Queries about the router itself are classified but handled by Opus (per CLAUDE.md rules). This is intentional - users discussing the router get the most capable model while still seeing what the classifier decided.Related Skills
routeros-qemu-chr
MikroTik RouterOS CHR (Cloud Hosted Router) with QEMU. Use when: running RouterOS in QEMU, booting CHR images, debugging CHR boot failures, setting up VirtIO devices for RouterOS, choosing between SeaBIOS and UEFI boot, configuring QEMU port forwarding for RouterOS REST API, or selecting QEMU acceleration (KVM/HVF/TCG).
routeros-netinstall
MikroTik netinstall-cli for automated RouterOS device flashing. Use when: automating netinstall, writing scripts that invoke netinstall-cli, building netinstall tooling, understanding etherboot/BOOTP/TFTP protocols, working with RouterOS package files (.npk), using modescript or configure script, or when the user mentions netinstall, etherboot, or device flashing.
routeros-fundamentals
RouterOS v7 domain knowledge for AI agents. Use when: working with MikroTik RouterOS, writing RouterOS CLI/script commands, calling RouterOS REST API, debugging why a Linux command fails on RouterOS, or when the user mentions MikroTik, RouterOS, CHR, or /ip /system /interface paths. Scope: RouterOS 7.x (long-term and newer) only — v6 is NOT covered and accuracy for v6 problems will be low.
routeros-container
RouterOS /container subsystem for running OCI containers on MikroTik devices. Use when: enabling containers on RouterOS, setting up VETH/bridge networking for containers, managing container lifecycle via CLI or REST API, building OCI images for RouterOS, configuring container environment variables, troubleshooting container issues, or when the user mentions RouterOS container, /container, VETH, device-mode container, or MikroTik Docker.
routeros-command-tree
RouterOS command tree introspection via /console/inspect API. Use when: building tools that parse RouterOS commands, generating API schemas from RouterOS, working with /console/inspect, mapping CLI commands to REST verbs, traversing the RouterOS command hierarchy, or when the user mentions inspect, command tree, RAML, or OpenAPI generation for RouterOS.
routeros-app-yaml
RouterOS /app YAML format for container applications (7.21+ builtin app, 7.22+ custom YAML creation). Use when: writing or validating RouterOS /app YAML files, working with MikroTik container apps, building docker-compose-like definitions for RouterOS, creating /app store schemas, debugging /app validation errors, or when the user mentions /app, tikapp, or RouterOS container YAML.
nextjs-app-router-patterns
Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Server Components.
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
mulerouter
Generates images and videos using MuleRouter or MuleRun multimodal APIs. Text-to-Image, Image-to-Image, Text-to-Video, Image-to-Video, video editing (VACE, keyframe interpolation). Use when the user wants to generate, edit, or transform images and videos using AI models like Wan2.6 or Nano Banana.
word-stats
Get word count, character count, reading time, and text statistics. Quick analysis without questions.
statsmodels
Statistical modeling toolkit. OLS, GLM, logistic, ARIMA, time series, hypothesis tests, diagnostics, AIC/BIC, for rigorous statistical inference and econometric analysis.
frontend-nextjs-app-router
Use when working with Next.js App Router tasks - creating pages in /app/, setting up dynamic routes ([id]/page.tsx), implementing nested layouts/templates (layout.tsx), optimizing Server/Client components, or building ERP role-based pages (admin/teacher/student dashboards). Auto-use for all /app/ directory operations, dynamic routing, and App Router-specific features.