sk-wwise-mcp: Skill for Claude Code

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

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

A test-only setup for creating a temporary Wwise audio project and filling it with sample sound objects, events, states, and switches.

In plain words
What is it for?
Use it to create the test project, start Wwise's background control server, check the connection, and build the sample audio hierarchy.
Why use it?
It gives evaluation tests a known Wwise project to work with, without changing a production project.

Skill for Claude Code

Written for Claude Code: disable-model-invocation 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-setup/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-setup

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/silver-rain-dev/sk-wwise-mcp/eval-setup"><img src="https://agentmods.dev/badge/skills/silver-rain-dev/sk-wwise-mcp/eval-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 617 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.00022 $0.00617
Opus 5.5 $0.00009 $0.00247
Sonnet 5.5 $0.00004 $0.00123
Haiku 4.5 $0.00002 $0.00062

Measured 2mo ago against content hash 62e45c1a77b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

eval-setup 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 2mo 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-setup/SKILL.md · 72 lines

How it starts

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

⚠️ TEST SETUP ONLY. Do NOT use for production. This creates a throwaway Wwise project and populates it with test objects.

Execute these steps in order using MCP tools. Stop if any step fails.

Step 1: Create test project and start headless WAAPI

  1. Use cli_create_new_project to create a fresh project at tests/eval/EvalTestProject/EvalTestProject.wproj
  2. Use cli_start_waapi_server to launch a headless WAAPI server with that project
  3. Wait 5 seconds, then ping Wwise to confirm connection
  4. Get project info to verify the project loaded

Step 2: Create Actor-Mixer hierarchy

Under \Containers\Default Work Unit, create:

  • ActorMixer "EvalTest_SFX"
    • RandomSequenceContainer "Footsteps" (set Volume to -6.0)
      • Sound "Footstep_01"
      • Sound "Footstep_02"
    • SwitchContainer "Weapons"
      • Sound "Sword_Hit"
      • Sound "Bow_Shot"
    • ActorMixer "Ambience"
      • Sound "Forest_Loop"
      • Sound "Wind_Loop"

Step 3: Create Events

Under \Events\Default Work Unit, create:

  • Folder "EvalTest_Events"
    • Event "Play_Footstep"
    • Event "Play_Sword"
    • Event "Play_Ambience"

Step 4: Create States and Switches

  • Under \States\Default Work Unit: StateGroup "PlayerHealth" with States: "Alive", "Low", "Dead"
  • Under \Switches\Default Work Unit: SwitchGroup "Surface" with Switches: "Grass", "Stone", "Wood"

Step 5: Set references

  • Set Weapons SwitchContainer to use SwitchGroup "Surface"
  • Assign Sword_Hit to "Grass" switch
  • Assign Bow_Shot to "Stone" switch

Step 6: Write setup manifest

Write the WAAPI server PID, project path, and created object paths to tests/eval/setup_manifest.json:

{
  "project_path": "tests/eval/EvalTestProject/EvalTestProject.wproj",
  "waapi_pid": <PID from cli_start_waapi_server>,
  "objects": {
    "actor_mixer": "\\Containers\\Default Work Unit\\EvalTest_SFX",
    "footsteps": "\\Containers\\Default Work Unit\\EvalTest_SFX\\Footsteps",
    "weapons": "\\Containers\\Default Work Unit\\EvalTest_SFX\\Weapons",
    "events_folder": "\\Events\\Default Work Unit\\EvalTest_Events"
  }
}

Read the full file on GitHub · 72 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. 2mo ago First seen · 72 lines · 22 tokens per session scan A 62e45c1a77b4

Subscribe to this mod's changes

eval-setup is a skill published in the GitHub repository silver-rain-dev/sk-wwise-mcp (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 617 once invoked, about $0.0001 per session on Opus 5.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.

Related

eval-setup compared with skills from other repositories

eval-setup next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
eval-setupsilver-rain-dev/sk-wwise-mcpSkill51mo agoApache-2.0A22Claude Code
opik-diagnosecomet-ml/opik-mcpSkill2259d agoApache-2.0A187Claude Code
ue-mcp-epic-routingdb-lyon/ue-mcpSkill476yesterdayMITA81Claude Code, Codex
qa-knowledgegriddynamics/rosettaSkill370yesterdayApache-2.0A32Claude Code, Codex
apitapn1byn1kt/apitapSkill13117d agoApache-2.0A0Claude Code, Codex
frontmcp-setupagentfront/frontmcpSkill148yesterdayApache-2.0A176Claude Code, Codex
x-use-reviewihuzaifashoukat/x-useSkill1814d agoMITA56Claude Code