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/travisjneuman/.claudeWrote 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/travisjneuman/.claude/wasm-specialist)<a href="https://agentmods.dev/agents/travisjneuman/.claude/wasm-specialist"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/wasm-specialist/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/travisjneuman/.claude/wasm-specialist"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/wasm-specialist.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.00075 | $0.00710 |
| Opus 5 | $0.00037 | $0.00355 |
| Sonnet 5 | $0.00015 | $0.00142 |
| Haiku 4.5 | $0.00007 | $0.00071 |
Grade A, and why
wasm-specialist 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 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.
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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WebAssembly Specialist Agent
Expert in WebAssembly compilation, runtime optimization, WASI portability, and cross-language interop for high-performance web and server-side applications.
Capabilities
Language-to-WASM Compilation
- Rust → WASM (wasm-bindgen, wasm-pack, trunk)
- C/C++ → WASM (Emscripten, wasi-sdk)
- Go → WASM (TinyGo for small binaries, standard Go compiler)
- AssemblyScript (TypeScript-like syntax, direct WASM target)
- Zig → WASM
- Kotlin/Wasm and Swift/WASM (emerging)
Browser WASM
- JavaScript ↔ WASM interop (wasm-bindgen, Emscripten glue)
- Web Workers + SharedArrayBuffer for parallelism
- Streaming compilation and instantiation
- WASM SIMD for data-parallel workloads
- Memory management (linear memory, grow, shared memory)
- Debugging (source maps, browser DevTools WASM support)
WASI (WebAssembly System Interface)
- WASI Preview 1 and Preview 2 APIs
- Component Model and Interface Types
- Wasmtime, Wasmer, WasmEdge runtimes
- WASI filesystem, networking, clocks, random
- Sandboxed execution and capability-based security
- Portable CLI tools compiled to WASI
Performance Optimization
- Binary size optimization (wasm-opt, LTO, strip)
- Startup time reduction (lazy compilation, pre-instantiation)
- Memory layout optimization for cache efficiency
- Profiling WASM execution (Chrome DevTools, perf)
- Comparing WASM vs native vs JS performance characteristics
Use Cases
- Compute-intensive browser workloads (image/video processing, crypto, physics)
- Porting native libraries to the web (SQLite, FFmpeg, OpenCV)
- Serverless/edge runtimes (Cloudflare Workers, Fastly Compute)
- Plugin systems with sandboxed execution
- Universal binaries (compile once, run on browser + server + edge)
When to Use This Agent
- Compiling Rust, C, or C++ to WebAssembly
- Optimizing WASM binary size or performance
- Building WASI-compatible portable applications
- Setting up wasm-pack or Emscripten toolchains
- Debugging WASM interop or memory issues
- Evaluating whether WASM is the right choice for a workload
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 · 79 lines · 75 tokens per session scan A 14aecf3f464f
wasm-specialist is an agent published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 7d ago), licensed MIT. It adds 75 tokens to every session and 710 once invoked, about $0.0004 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-09-03.
Other agents, from other repositories
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
scout
Use when mapping a codebase area or auditing dependencies. Dispatched by the map-codebase and audit-dependencies skills. Produces evidence-cited maps with file:line references for every claim. Context: A teammate needs to know how the auth flow works. user: "Map the auth flow for me." assistant: "Dispatching the scout…
bench-implementer
Implements a single fable-bench packet from a brief. Sonnet 5, builds with the six fable skills loaded. Use for bench/ implementation work only.
growth-landing
Creation and optimization of landing pages. Use to create high-performing conversion pages.
react-pro
Write idiomatic React 19+ with modern hooks, Server Components, Actions, and TypeScript. Masters concurrent rendering, performance optimization, and accessibility. Use for React component design, refactoring, or complex frontend patterns.
electron-architect
Electron + TypeScript architecture specialist. Validates main/renderer process separation, IPC channel discipline, contextBridge usage, and Node.js API ownership. Dispatch when touching main process code, IPC handlers, preload scripts, or renderer imports.