Get the FREE Ultimate OpenClaw Setup Guide →

router-stats

Scanned
npx machina-cli add skill aiskillstore/marketplace/router-stats --openclaw
Files (1)
SKILL.md
3.8 KB

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):

{
  "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.

Source

git clone https://github.com/aiskillstore/marketplace/blob/main/skills/0xrdan/router-stats/SKILL.mdView on GitHub

Overview

This skill reads the router statistics file and renders a clear report of routing usage, exceptions, and estimated savings. It highlights total queries, route distribution (fast, standard, deep, orchestrated), tool-intensive and orchestrated queries, and overall cost impact.

How This Skill Works

It loads the v1.2 router-stats.json from ~/.claude, computes route share percentages and per-session savings, and formats a ready-to-share ASCII report. It surfaces today’s snapshot, all-time totals, and the cost-savings breakdown to help optimize routing decisions.

When to Use It

  • Audit router usage over a period to optimize routing decisions
  • Share a stakeholder-friendly view of costs and savings
  • Identify skew in route distribution (fast vs standard vs deep vs orchestrated)
  • Compare today’s metrics against all-time totals
  • Verify exceptions handling and Opus-based routing implications

Quick Start

  1. Step 1: Read the stats file at ~/.claude/router-stats.json
  2. Step 2: If the file doesn't exist, inform that no stats are available yet
  3. Step 3: Generate and display the formatted report with calculated percentages

Best Practices

  • Ensure the stats file exists at ~/.claude/router-stats.json before running
  • Run on a regular cadence and check the last_updated timestamp
  • Compute and review route distribution percentages for each category
  • Include exception counts (router_meta and slash_commands) when present
  • Compare estimated_savings, delegation_savings, and total savings to gauge impact

Example Use Cases

  • Weekly dashboard showing total queries, route distribution, and savings
  • Today’s snapshot with the number of queries and per-route usage
  • Per-session breakdown to identify peak usage times and adjust prompts
  • Savings analysis showing how much could be saved by routing more to Opus
  • Alert-style view when router_meta exceptions spike unexpectedly

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers