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/verifynpx skills add perminder-klair/subwave --skill verifygit clone --depth 1 https://github.com/perminder-klair/subwaveWrote 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/perminder-klair/subwave/verify)<a href="https://agentmods.dev/skills/perminder-klair/subwave/verify"><img src="https://agentmods.dev/badge/skills/perminder-klair/subwave/verify.svg" alt="Measured on agentmods" 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 | $0.00045 | $0.00462 |
| Opus 5 | $0.00023 | $0.00231 |
| Sonnet 5 | $0.00009 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
verify 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 4d 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.
- Drive `/settings` etc. with `curl -u test:test http://localhost:7791/...`. What it actually says
Verifying controller + admin-UI changes in isolation
The operator's real station is usually running (docker sub-wave-* containers). Never restart or
point tests at it. Boot your own stack from the worktree instead:
Isolated controller (API surface)
cd <worktree>/controller
STATE_DIR=$CLAUDE_JOB_DIR/tmp/state PORT=7791 ADMIN_USER=test ADMIN_PASS=test \
NODE_ENV=development \
NAVIDROME_URL=http://localhost:9999 NAVIDROME_USER=x NAVIDROME_PASS=x \
npx tsx src/server.ts
- A fresh
STATE_DIRboots clean (seeds sfx/jingles, writessettings.jsonon first save). - The fake
NAVIDROME_*env matters: without itneedsSetupis true and the admin shell redirects every page to/onboarding, so UI tests never find their controls. - Drive
/settingsetc. withcurl -u test:test http://localhost:7791/.... - To test load-time migrations: stop the server, hand-edit
settings.json, restart, GET. - Kill by port (
fuser -k 7791/tcp) — apkill -f "tsx src/server.ts"matches the Bash tool's own wrapper cmdline and kills your shell (exit 144).
Worktree web dev server (UI surface)
cd <worktree>/web
NEXT_PUBLIC_API_URL=http://localhost:7791 npm run dev -- -p 7793
Then Playwright (headless chromium, sync API):
- Pre-seed auth before load:
ctx.add_init_script("localStorage.setItem('subwave_admin_auth', '<base64 user:pass>')"). - Assert state through the controller API after clicking Save, not through sonner toasts.
- Admin modals portal into
.admin-root; scope input lookups with[role="dialog"].
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.
- 4d ago First seen · 41 lines · 45 tokens per session scan A 7d18ebc94bc1
verify is a skill published in the GitHub repository perminder-klair/subwave (1,298 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 462 once invoked, about $0.0002 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
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
google-safe-browsing
Prevent and fix Google Safe Browsing "Dangerous site" flags. Use when launching a public web app, buying/picking a domain, building a login or signup page, or when any site shows a red "Dangerous site" / "Deceptive site" warning in Chrome, Brave, Safari, Firefox, or Edge. Triggers on "dangerous site", "deceptive…
web-browser
Automate and interact with web pages through Chrome or Chromium using the Chrome DevTools Protocol (CDP): navigate, click, fill forms, inspect content, take screenshots, and debug console or network activity. Use when an agent needs a real browser. Prefer headless Chrome unless visible browser interaction is required.