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-pack-buildWrote 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-pack-build)<a href="https://agentmods.dev/skills/gertsylvest/meta-team/wasm-pack-build"><img src="https://agentmods.dev/badge/skills/gertsylvest/meta-team/wasm-pack-build/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-pack-build"><img src="https://agentmods.dev/badge/skills/gertsylvest/meta-team/wasm-pack-build.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.00076 | $0.01030 |
| Opus 5 | $0.00038 | $0.00515 |
| Sonnet 5 | $0.00015 | $0.00206 |
| Haiku 4.5 | $0.00008 | $0.00103 |
Grade A, and why
wasm-pack-build 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wasm-pack Build
The canonical Rust→WASM build path for browser audio. Builds with wasm-pack against wasm32-unknown-unknown, applies wasm-opt for size and performance, and runs wasm-module-inspect on the output to confirm exports are minimal, SIMD is present, and the module validates.
The flag set is fixed by this skill so every Rust WASM build in the project produces a binary with the same characteristics — no ad-hoc differences between developer machines or CI.
Requirements
- rustup with stable toolchain and the
wasm32-unknown-unknowntarget:rustup target add wasm32-unknown-unknown - wasm-pack — install via
cargo install wasm-packor from https://rustwasm.github.io/wasm-pack/installer/. - wasm-opt (Binaryen) — install via
brew install binaryen(macOS) orapt install binaryen(Linux). - The
wasm-module-inspectskill from this library (the script invokes it for the final verification step).
What it does
- Verifies prerequisites (
wasm-pack,wasm-opt, target installed). - Sets
RUSTFLAGS="-C target-feature=+simd128"so WASM SIMD is enabled. - Runs
wasm-pack build --target web --release(or--devif--devis passed) on the crate. - Runs
wasm-opt -O3 --enable-simd <pkg>/<crate>_bg.wasm -o <same>to apply Binaryen's optimisation pass over the wasm-bindgen-emitted module. - Invokes
wasm-module-inspecton the optimised.wasm.
Release builds also implicitly use the project's [profile.release] settings — the crate is expected to declare panic = "abort", lto = "fat", codegen-units = 1, opt-level = 3 per the rust-audio-engineer agent's standards.
Instructions
The arguments are in $ARGUMENTS. Pass them directly to the build script:
bash "$(dirname "$0")/build.sh" $ARGUMENTS
Argument 1 is the crate directory. Optional second argument --dev switches to a debug build with source maps for browser debugging.
Output sections
| Section | What it reports |
|---|---|
PREREQ |
Whether wasm-pack, wasm-opt, and the wasm32 target are present |
BUILD |
wasm-pack invocation result |
OPTIMISE |
wasm-opt size reduction |
INSPECT |
Full output of wasm-module-inspect |
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 · 74 lines · 76 tokens per session scan A a98e0f45de1e
wasm-pack-build is a skill published in the GitHub repository gertsylvest/meta-team (5 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 1,030 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-08-31.
Other skills, from other repositories
rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
omh-rust
This is a Hermes-native rust workflow skill.
bevy-ecs
Structure a Bevy app around its Entity Component System: build the App with plugins, define Component/Resource types, write systems with Query/Res/Commands, filter and order systems, and use the Time resource for frame-rate-independent motion. Use when building or debugging a Bevy game in Rust — when the user mentions…
rust-project
Modern Rust project architecture guide for 2025. Use when creating Rust projects (CLI, web services, libraries). Covers workspace structure, error handling, async patterns, and idiomatic Rust best practices.
gcs-rust-download-object-api
Fix "DownloadObjectRequest not found" error in google-cloud-storage Rust crate. Use when: (1) Trying to download objects from GCS using the Rust SDK, (2) Looking for a download request type in http::objects::download module, (3) Compile error about missing type. The downloadobject method uses GetObjectRequest from the…