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 damionrashford/media-os --skill audio-routing-docsgit clone --depth 1 https://github.com/damionrashford/media-osWrote 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/damionrashford/media-os/audio-routing-docs)<a href="https://agentmods.dev/skills/damionrashford/media-os/audio-routing-docs"><img src="https://agentmods.dev/badge/skills/damionrashford/media-os/audio-routing-docs/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/damionrashford/media-os/audio-routing-docs"><img src="https://agentmods.dev/badge/skills/damionrashford/media-os/audio-routing-docs.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.00189 | $0.02816 |
| Opus 5 | $0.00095 | $0.01408 |
| Sonnet 5 | $0.00038 | $0.00563 |
| Haiku 4.5 | $0.00019 | $0.00282 |
Grade A, and why
audio-routing-docs 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audio Routing Docs
Context: $ARGUMENTS
Quick start
- Find a command / API: → Step 2 (
search --query <term>) - Read the full section for one command: → Step 3 (
section --page <name> --id <anchor>) - Grab an entire doc page: → Step 4 (
fetch --page <name>) - Prime the cache for offline use: → Step 5 (
index) - List all known pages grouped by host: → Step 1 (
list-pages)
When to use
- User asks "what does
pw-link/jack_connect/SwitchAudioSource/svcl.exedo?" - Need to verify a subsystem CLI flag before recommending it (anti-hallucination guard).
- Need the canonical URL for a PipeWire man page, JACK API doc, Apple Core Audio archive page, or Microsoft WASAPI concept page.
- About to write instructions involving virtual drivers (BlackHole, VB-Cable, VoiceMeeter) and want the real install/config page, not a guess.
This skill is docs only. For actual capability (running pw-link, installing
BlackHole, flipping Windows default output), use the sibling skills:
audio-pipewire, audio-jack, audio-coreaudio, audio-wasapi.
Step 1 — Know the page catalog
The script works only against a curated list of pages across four hosts:
docs.pipewire.org, jackaudio.org, developer.apple.com, learn.microsoft.com.
Get the current list:
uv run ${CLAUDE_SKILL_DIR}/scripts/audiodocs.py list-pages
Common picks by question:
| Question | Page |
|---|---|
"What does pw-link accept?" |
pipewire-man-pw-link |
| "How do I dump the PipeWire graph?" | pipewire-man-pw-dump |
| "Where are PipeWire CLIs listed?" | pipewire-programs |
| "WirePlumber session manager?" | wireplumber-home |
"What is jack_lsp?" |
jack-api or jack-stanford |
| "JackTrip over the internet?" | jacktrip-docs, jacktrip-github |
| "What is Core Audio / the HAL?" | coreaudio-overview, coreaudio-essentials |
| "SwitchAudioSource flags?" | switchaudio-osx |
| "BlackHole install?" | blackhole-github |
| "WASAPI exclusive vs shared?" | wasapi-exclusive, wasapi-overview |
| "NirSoft svcl.exe flags?" | wasapi-svcl |
| "AudioDeviceCmdlets PowerShell?" | wasapi-audiodevicecmdlets |
| "VB-Cable / VoiceMeeter install?" | wasapi-vbcable, wasapi-voicemeeter |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 280 lines · 189 tokens per session scan A a20107bc0ad1
audio-routing-docs is a skill published in the GitHub repository damionrashford/media-os (18 stars, last pushed 3mo ago), licensed MIT. It adds 189 tokens to every session and 2,816 once invoked, about $0.0009 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
telephony-and-conferencing
Runs voice and meeting infrastructure — phone systems and numbers, emergency calling obligations, conference rooms and their AV, call recording and its retention consequences, and the porting that makes provider changes go badly. Use this to replace a phone system, fix rooms nobody can start a meeting in, meet…
endpoint-management
Manages laptops, desktops and mobile devices — enrollment, configuration, patching, software distribution, and lost or compromised devices. Use this to set up device management, standardize builds, roll out software or an OS upgrade, handle a lost device, or bring an unmanaged fleet under control.
keenetic-segments
Use when creating an isolated network on a Keenetic - a guest network, an IoT network, a segment routed through a VPN - explains why the obvious way produces a working network the web interface refuses to list, and the VLAN it is actually missing.
keenetic-rci
Use when a Keenetic question is not covered by the curated tools and you need rcicall - explains the RCI tree, the paths that exist, the responses that will blow up your context, and the traps that make a wrong call look like success.
keenetic-troubleshoot
Use when someone reports the internet is down, Wi-Fi is bad, a device cannot connect, or the network is slow on a Keenetic router - an ordered playbook that narrows the fault instead of guessing.
keenetic-safe-changes
Use before changing anything on a Keenetic router - explains that changes are not saved until asked, what the router's fail-safe does and does not protect against, and the order that avoids locking yourself out.