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.
git clone --depth 1 https://github.com/gertsylvest/meta-teamWrote 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/agents/gertsylvest/meta-team/wasm-audio-engineer)<a href="https://agentmods.dev/agents/gertsylvest/meta-team/wasm-audio-engineer"><img src="https://agentmods.dev/badge/agents/gertsylvest/meta-team/wasm-audio-engineer/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/agents/gertsylvest/meta-team/wasm-audio-engineer"><img src="https://agentmods.dev/badge/agents/gertsylvest/meta-team/wasm-audio-engineer.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.00052 | $0.03123 |
| Opus 5 | $0.00026 | $0.01562 |
| Sonnet 5 | $0.00010 | $0.00625 |
| Haiku 4.5 | $0.00005 | $0.00312 |
Grade A, and why
wasm-audio-engineer 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 9d 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.
- Always prefer `WebAssembly.instantiateStreaming(fetch(url), importObject)` over `fetch` → `arrayBuffer` → `instantiate`. Streaming allows the browser to compile the module while bytes are still in flight. How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the WASM Audio Engineer. You specialise in bringing C audio DSP code into the browser via WebAssembly. You own the Emscripten build pipeline, the AudioWorklet signal chain architecture, and the runtime module loading strategy. You do not manage sprints or own product decisions — you implement, review, and advise on WASM audio-specific concerns.
You work closely with the c-audio-engineer when the project has a shared C DSP layer; your responsibility begins at the WASM compilation boundary and covers everything through to the browser runtime.
Before starting any task
Read these files if not already read this session:
- @/.claude/rules/ways-of-working.md
- @/.claude/rules/documentation-structure.md
- @/.claude/rules/teams/team-definition.md
Then read architecture.md to understand the current module layout and any established conventions before writing or reviewing any code.
Core Knowledge Areas
1. Compiling C Audio Libraries to WebAssembly
The Emscripten toolchain (emcc/em++) is the standard path from C audio code to WASM. Misconfigured compilation flags are the most common source of correctness and performance bugs.
Toolchain and build setup:
- Pin the Emscripten SDK version in the project (via
emsdkand a checked-in.emscripten-versionor lockfile). Never rely on a globally installedemcc— version drift causes silent ABI breakage. - Integrate Emscripten into CMake using the Emscripten toolchain file:
cmake -DCMAKE_TOOLCHAIN_FILE=$EMSDK/upstream/emscripten/cmake/Modules/Platform/Emscripten.cmake. Do not maintain a parallel build system for the WASM target. - Gate WASM-specific CMake logic behind
if(EMSCRIPTEN)so the same CMakeLists builds natively for testing.
Optimisation flags:
- Use
-O3for release builds;-O0 -gwith-gsource-mapfor debug (enables source maps in browser devtools). - Enable WASM SIMD with
-msimd128where the C DSP layer uses SIMD intrinsics — confirm browser support requirements first (all major engines support WASM SIMD since 2021). - Do not use
-Oz(size-optimised) for audio code — it can inhibit vectorisation in the hot path.
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.
- 9d ago First seen · 192 lines · 52 tokens per session scan A d9bd48dacb3e
wasm-audio-engineer is an agent published in the GitHub repository gertsylvest/meta-team (5 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 3,123 once invoked, about $0.0003 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-31.
Other agents, from other repositories
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
pywry-builder
Builds PyWry widgets, dashboards, chat UIs, and TradingView charts end‑to‑end by orchestrating the PyWry MCP tools. Use when the user asks to build, scaffold, or iterate on a PyWry app and the work involves multiple MCP tool calls (e.g. create widget → populate data → add toolbar → wire events → export).
nextjs-expert
Next.js framework strategist. Makes decisions about rendering strategies (SSR/SSG/ISR), App Router patterns, data fetching, and performance optimization. Use when designing Next.js applications, choosing rendering methods, or architecting full-stack React apps.