sk-wwise-mcp: Skill for Claude Code

.claude/skills/eval-routing/SKILL.md

eval-routing is a skill for Claude Code from silver-rain-dev/sk-wwise-mcp. It costs 21 tokens per session (661 once invoked), scanned A, original, Apache-2.0.

A test-only procedure that checks one tool-routing decision at a time and records the results.

In plain words
What is it for?
Use it to find the next untested case, evaluate every case in order, detect stale results, and create a final report.
Why use it?
It makes it possible to inspect routing behavior case by case and continue across multiple runs without losing progress.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

This is silver-rain-dev/sk-wwise-mcp's own configuration. It tells Claude Code how to work on sk-wwise-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything sk-wwise-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to silver-rain-dev/sk-wwise-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/silver-rain-dev/sk-wwise-mcp/main/.claude/skills/eval-routing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/silver-rain-dev/sk-wwise-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for eval-routing

README.md
[![agentmods](https://agentmods.dev/badge/skills/silver-rain-dev/sk-wwise-mcp/eval-routing/github.svg)](https://agentmods.dev/skills/silver-rain-dev/sk-wwise-mcp/eval-routing)
Your own site
<a href="https://agentmods.dev/skills/silver-rain-dev/sk-wwise-mcp/eval-routing"><img src="https://agentmods.dev/badge/skills/silver-rain-dev/sk-wwise-mcp/eval-routing/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.

agentmods 80×15 button for eval-routing

Your own site · 80×15
<a href="https://agentmods.dev/skills/silver-rain-dev/sk-wwise-mcp/eval-routing"><img src="https://agentmods.dev/badge/skills/silver-rain-dev/sk-wwise-mcp/eval-routing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 661 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.00661
Opus 5 $0.00010 $0.00331
Sonnet 5 $0.00004 $0.00132
Haiku 4.5 $0.00002 $0.00066

Measured 9d ago against content hash d78cbfe4b250, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

eval-routing 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 9d 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.

.claude/skills/eval-routing/SKILL.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

This is a TEST/EVAL SKILL ONLY. Do NOT use for production MCP usage. This skill evaluates tool routing decisions one case at a time.

Running all cases automatically

Use /loop to iterate through every test case unattended:

/loop 30s /eval-routing

This invokes /eval-routing every 30 seconds, advancing one case per iteration. When all cases are tested the skill prints "All cases evaluated", auto-generates the report, and tells you to stop the loop.

Instructions (single case)

  1. Read tests/eval/test_cases.json to get all test cases

  2. Read tests/eval/test_results.json to find which cases have already been tested

    • If the file doesn't exist, no cases have been tested yet
  3. Stale-result guard: If ALL cases already have results, auto-reset by running: python tests/eval/verify.py --check-stale This will detect stale results (from a prior session) and reset automatically. Then re-read test_results.json (it will now be empty).

  4. Find the next case (by id) that has no entry in test_results

  5. If all cases are tested:

    • Run python tests/eval/report.py to generate the report inline
    • Print "All cases evaluated" and tell the user to stop the loop (CronDelete <id>)
    • Stop — do not run any more cases
  6. Clear tests/eval/tool_log.jsonl (write empty string to it)

  7. Now handle the test case prompt as if a real user asked it:

    • The prompt is in the "prompt" field of the test case
    • Use MCP tools normally to fulfill the request
    • For write operations (create, delete, move), always clean up after:
      • Check if the case has a "cleanup" field in test_cases.json
      • If cleanup.tool is "set_wwise_object_properties": restore the original value using set_wwise_object_properties(operations=[{"object": cleanup.object, "properties": {cleanup.property: cleanup.restore_value}}])
      • If cleanup.tool is "set_wwise_object_name": rename back using set_wwise_object_name(object=cleanup.object_after, value=cleanup.restore_name)
      • If cleanup.bulk_restore exists: iterate and restore each entry
      • If no cleanup field: use your judgment (e.g., delete created objects)
    • Cases with "expected_error": true will have the tool fail at runtime — that's OK. The eval only checks routing (which tools were called), not whether they succeeded.

Read the full file on GitHub · 56 lines

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.

  1. 9d ago First seen · 56 lines · 21 tokens per session scan A d78cbfe4b250

Subscribe to this mod's changes

eval-routing is a skill published in the GitHub repository silver-rain-dev/sk-wwise-mcp (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 661 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-31.