Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/gertsylvest/meta-teamnpx agentmods add skills/gertsylvest/meta-team/wasm-worklet-smokeWrote 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/gertsylvest/meta-team/wasm-worklet-smoke)<a href="https://agentmods.dev/skills/gertsylvest/meta-team/wasm-worklet-smoke"><img src="https://agentmods.dev/badge/skills/gertsylvest/meta-team/wasm-worklet-smoke/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/gertsylvest/meta-team/wasm-worklet-smoke"><img src="https://agentmods.dev/badge/skills/gertsylvest/meta-team/wasm-worklet-smoke.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.00064 | $0.01384 |
| Opus 5 | $0.00032 | $0.00692 |
| Sonnet 5 | $0.00013 | $0.00277 |
| Haiku 4.5 | $0.00006 | $0.00138 |
Grade A, and why
wasm-worklet-smoke 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WASM Worklet Smoke Test
Automated headless verification of an Emscripten + AudioWorklet build. Catches the class of failures that require a browser to surface: worklet registration failures, Emscripten runtime errors (self is not defined, fetch is not a function), WASM instantiation failures, and silent audio output.
Covers the gaps in a basic log-message-only smoke test: verifies actual audio output is non-silent, verifies the parameter message path, and catches all console.error / unhandled rejection events.
Requirements
- Node.js 18+ and npm
- Playwright with Chromium:
npm install playwright && npx playwright install chromium - Python 3 (for the HTTP server)
- make with a WASM build target (default:
synth-wasm) - Project setup:
main.jsmust exposewindow.__audioCtxandwindow.__synthNodefor audio verification (see Project Setup below)
Project setup
The audio verification step reads audioCtx and synthNode from window. The IIFE in main.js hides these by default. Add the following lines inside the IIFE after the AudioWorkletNode is connected and ready:
// Expose for automated testing (safe: AudioWorkletGlobalScope is isolated)
if (typeof window !== 'undefined') {
window.__audioCtx = audioCtx;
window.__synthNode = synthNode;
}
Guard with window.__TEST_MODE if you prefer to enable this only during tests:
if (window.__TEST_MODE) {
window.__audioCtx = audioCtx;
window.__synthNode = synthNode;
}
If the audio check is not needed, pass --no-audio-check to skip this step and the project setup requirement.
Instructions
Arguments are in $ARGUMENTS. Pass them directly to the smoke test script:
node "$(dirname "$0")/smoke.js" $ARGUMENTS
What the test verifies
| Check | What it catches |
|---|---|
| Build succeeds | Compilation errors in any source file, missing include paths |
| Server starts | Broken asset copy, missing synth.js / synth.wasm |
WASM engine initialised log |
Worklet registered, WASM instantiated, onRuntimeInitialized fired |
Zero console.error events |
Any runtime JS error in the worklet or main thread |
Zero pageerror events |
Uncaught exceptions |
| Non-silent audio (AnalyserNode) | Silent engine (stuck envelope, null DSP output, broken computeSynth call) |
| Expected fundamental frequency | Wrong oscillator frequency, detuning bug, wrong default param |
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.
- 11d ago First seen · 112 lines · 64 tokens per session scan A 872731a81529
wasm-worklet-smoke is a skill published in the GitHub repository gertsylvest/meta-team (5 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 1,384 once invoked, about $0.0003 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.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…