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 skills add Goldziher/ai-rulez --skill wasm-bindingsgit clone --depth 1 https://github.com/Goldziher/ai-rulezWrote 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/goldziher/ai-rulez/wasm-bindings)<a href="https://agentmods.dev/skills/goldziher/ai-rulez/wasm-bindings"><img src="https://agentmods.dev/badge/skills/goldziher/ai-rulez/wasm-bindings/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/goldziher/ai-rulez/wasm-bindings"><img src="https://agentmods.dev/badge/skills/goldziher/ai-rulez/wasm-bindings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00330 |
| Opus 5 | $0.00032 | $0.00165 |
| Sonnet 5 | $0.00013 | $0.00066 |
| Haiku 4.5 | $0.00006 | $0.00033 |
Grade A, and why
wasm-bindings 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.
What it actually says
- Use
wasm-bindgenfor JavaScript interop. Usewasm-packfor building and packaging. - Map Rust types to JS with
#[wasm_bindgen]. UseJsValuefor dynamic types, typed wrappers for known types. - Handle errors with
Result<T, JsValue>. Convert Rust errors to descriptive JS error messages. - Support both browser (ES modules) and Node.js (CommonJS/ESM) targets.
- Async: use
wasm-bindgen-futuresfor Promise-returning functions. Never block the main thread. - Bundle size: use
opt-level = "z",lto = true,codegen-units = 1in release profile. - Use
web-sysandjs-sysfor Web API access. Feature-gate platform-specific APIs. - Test with
wasm-pack test --headless --firefoxand a JS test runner (e.g., Vitest or Jest) for JS integration tests. - Generate TypeScript definitions automatically. Keep
.d.tsfiles in sync with Rust exports. - Anti-patterns: no
std::thread(single-threaded), no synchronous I/O, no panics (becomes JS exception).
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 · 16 lines · 64 tokens per session scan A 71001c6c8e05
wasm-bindings is a skill published in the GitHub repository Goldziher/ai-rulez (141 stars, last pushed 3d ago), licensed MIT. It adds 64 tokens to every session and 330 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-30.
Other skills, from other repositories
printing-press-polish
Polish a generated CLI to pass verification and become publish-ready. Runs diagnostics (dogfood, verify, scorecard, go vet, gosec), automatically fixes all issues (verify failures, static-analysis findings, dead code, descriptions, README, MCP tool quality), reports the before/after delta, and offers to publish. Use…
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
printing-press
Set up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says build a CLI, wrap this API, set up a new integration, add a connector, integrate with a…
gograph
Go repository intelligence for Claude Code. Use when reading, navigating, editing, reviewing, or refactoring a Go codebase. Exposes 64 query, analysis, and workflow capabilities through the local gograph MCP server, including bounded first-call exploration, AST-aware call graphs, blast-radius analysis, impact, and…
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…