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 agentmods add skills/perminder-klair/subwave/subwave-worktree-devnpx skills add perminder-klair/subwave --skill subwave-worktree-devgit clone --depth 1 https://github.com/perminder-klair/subwaveWhat 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 | $0.00196 | $0.02186 |
| Opus 5 | $0.00098 | $0.01093 |
| Sonnet 5 | $0.00039 | $0.00437 |
| Haiku 4.5 | $0.00020 | $0.00219 |
Grade A, and why
subwave-worktree-dev scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf http://localhost:7701/health # expect {"status":"on-air"} How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SUB/WAVE worktree dev setup
Get the SUB/WAVE dev stack running from inside a git worktree so branch changes can be tested without touching the main checkout.
Why a worktree needs prep
A worktree checks out every tracked file, so all source is already there. But the dev stack also depends on gitignored files that do not travel with a worktree checkout:
| File | Why the stack needs it |
|---|---|
.env |
Root .env — ADMIN_USER / ADMIN_PASS / SITE_URL. Dev compose references it as ./.env; compose refuses to start without it. |
controller/.env |
Dev compose declares env_file: ./controller/.env — controller container won't start without it. Navidrome + Ollama config. |
web/.env.local |
Dev API/stream URL overrides (NEXT_PUBLIC_API_URL etc.). Without it the web UI defaults to same-origin /api and cannot reach the controller. |
docker/.env |
Compose variable substitution (legacy — harmless to copy). |
state/setup-config.json |
Navidrome creds the wizard saved on main. Without this the controller reports needsSetup: true and the player redirects to /onboarding on every load. |
state/secrets.env |
Cloud LLM / TTS API keys (if main has any). Sourced into the controller's process.env on boot. |
state/settings.json |
Operator's full config — LLM provider/model, personas, shows, TTS. Without it the controller boots with default settings (llm.model = ''), every LLM call returns "fetch failed", and the new skills cannot run. |
state/moods.json |
Library mood tagging produced by npm run tag (LLM walk over the whole library — expensive to redo per branch). |
state/sfx.json + sfx/ |
Sound-effects catalogue metadata + rendered WAVs the admin UI lists and liquidsoap mixes in. |
state/jingles.json + jingles.m3u + jingles/ |
Pre-rendered station idents. Liquidsoap reads the M3U with reload_mode="watch". |
state/recent-plays.json |
24h play log — the picker and the library-deep-cut skill key off it for dedup. |
state/sessions/ |
Archived DJ sessions (the live one is regenerated on boot). |
state/voice/ |
Persona TTS reference voices (Chatterbox cloning refs, if any). |
web/node_modules |
Needed by npm run dev. |
state/ |
Bind-mounted into the containers. A worktree's state/ is empty. |
What ships with it
1 file 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.
- 3d ago First seen · 171 lines · 196 tokens per session scan A c7da0e63322b
subwave-worktree-dev is a skill published in the GitHub repository perminder-klair/subwave (1,287 stars, last pushed 3d ago), licensed MIT. It adds 196 tokens to every session and 2,186 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…