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 vosslab/vosslab-skills --skill wasm-rust-expertgit clone --depth 1 https://github.com/vosslab/vosslab-skillsWrote 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/vosslab/vosslab-skills/wasm-rust-expert)<a href="https://agentmods.dev/skills/vosslab/vosslab-skills/wasm-rust-expert"><img src="https://agentmods.dev/badge/skills/vosslab/vosslab-skills/wasm-rust-expert/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/vosslab/vosslab-skills/wasm-rust-expert"><img src="https://agentmods.dev/badge/skills/vosslab/vosslab-skills/wasm-rust-expert.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.00060 | $0.01113 |
| Opus 5 | $0.00030 | $0.00557 |
| Sonnet 5 | $0.00012 | $0.00223 |
| Haiku 4.5 | $0.00006 | $0.00111 |
Grade A, and why
wasm-rust-expert 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wasm Rust expert
Overview
Use this skill to take a Rust-to-WebAssembly request from target selection through browser integration, measurable performance work, and an executable comparison. Start from the shipped runtime and browser boundary: target triple, package tool, JavaScript bindings, browser APIs, and the computation that must agree with native Rust. Keep Rust computation portable and make the browser adapter a narrow, typed boundary. Use current wasm-bindgen, Rust target, MDN WebAssembly, browser, and WASI documentation for version-sensitive behavior; local books add concepts and worked examples when present.
Workflow
- Classify the Wasm target and route the request.
- Name the runtime: browser, WASI, embedded host, or another WebAssembly environment.
- Name the integration surface: wasm-bindgen export, wasm-pack package, web-sys API, Canvas loop, JavaScript data exchange, target setup, or performance measurement.
- Consult references/topic_index.md for the default tools, current-documentation route, and executable oracle.
- Read references/task_selection.md when Rust, TypeScript, Solid, or WebAssembly ownership needs a precise handoff.
- Detect the project shape and establish its Wasm contract.
- Inspect Cargo manifests, target configuration, generated package files, browser entry points, JavaScript or TypeScript bindings, and existing tests before changing code.
- Record the target triple, package command, host API boundary, supported browsers or runtime, data ownership, error surface, and performance budget in the project documentation.
- Read references/project_workflow.md for the greenfield wasm-pack path and the existing-crate browser-target path.
- Build the smallest vertical slice and preserve a portable computation core.
- Put deterministic domain computation in an ordinary Rust module that native tests can call.
- Add a focused wasm-bindgen or WASI adapter that converts host values at one boundary.
- Build one observable browser or runtime path before expanding API breadth.
What ships with it
7 files 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.
- 9d ago First seen · 92 lines · 60 tokens per session scan A 783786d16dba
wasm-rust-expert is a skill published in the GitHub repository vosslab/vosslab-skills (2 stars, last pushed 13d ago), licensed MIT. It adds 60 tokens to every session and 1,113 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
wasm-expert
WebAssembly expert for WASI, component model, Rust/C compilation, and browser integration.
gpui
GPUI framework knowledge covering actions/keybindings, async/background tasks, context management (App/Window/Context /AsyncApp), custom elements (low-level Element trait), entity state management, event system, focus handling, global state, layout/styling (flexbox/CSS-like), and testing. Use when working with any…
gpui-toolkit
Use when building or modifying GPUI applications in the gpui-toolkit workspace, especially when choosing reusable toolkit crates, composing UI, adding components, charts, themes, layouts, audio controls, mobile surfaces, or validation coverage. Prefer existing toolkit APIs over custom one-off implementations.
tauri-expert
Expert in Tauri framework, Rust backend, web frontend integration, and lightweight desktop applications. Use when the user mentions desktop, Rust, web, cross platform, or performance, or when the task involves Tauri Architecture, Tauri vs Electron, Core Components, or Security Features.
dioxus-knowledge-patch
Use this skill when creating, migrating, debugging, testing, or packaging a Dioxus application. Inspect manifests and the target platform, then open the matching topic reference.
webassembly-expert
Create production-ready WebAssembly modules for web and server environments with optimal performance and seamless JavaScript integration. Use when the user mentions WebAssembly or Wasm, WASI, compiling Rust/C/C++ to the browser, Emscripten, wasmtime, or JavaScript-to-Wasm interop for performance-critical code.