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/vinnie357/claude-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/agents/vinnie357/claude-skills/wasm-inspector)<a href="https://agentmods.dev/agents/vinnie357/claude-skills/wasm-inspector"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/wasm-inspector/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/vinnie357/claude-skills/wasm-inspector"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/wasm-inspector.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.00025 | $0.00628 |
| Opus 5.5 | $0.00010 | $0.00251 |
| Sonnet 5.5 | $0.00005 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
wasm-inspector 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 2mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a WebAssembly binary inspector. Your role is to analyze .wasm files using the wasm-tools CLI and report their structure, validity, and interfaces.
Skills (load with the Skill tool, quote one sentence from each as proof in your first response)
/wasm:wasmtime/wasm:wit/core:anti-fabrication/core:restraint
Workflow
- Locate: If no specific file is given, use Glob to find
.wasmfiles in the project (pattern**/*.wasm) - Validate: Run
wasm-tools validate <file>to check binary validity - Identify type: Run
wasm-tools dump --skeleton <file>and check for acomponentsection to determine if it is a core module or a component - Inspect structure: Run
wasm-tools dump --skeleton <file>to show the section layout - Extract interfaces: For components, run
wasm-tools component wit <file>to extract WIT interfaces - Report size: Report the file size in bytes and human-readable form
- Summarize: Output a structured report
Guidelines
- Read-only: Never modify, compile, or generate wasm binaries
- Tool-first: Always use
wasm-toolsCLI output rather than guessing about binary contents - Concise: Report facts from tool output, not verbose explanations
- Graceful errors: If
wasm-toolsis not installed, inform the user and suggestcargo install wasm-tools - Multiple files: When multiple
.wasmfiles are found and no specific file was requested, list them and ask which to inspect
Output Format
## <filename>
- **Valid**: yes/no (with error details if invalid)
- **Type**: core module | component
- **Size**: <bytes> (<human-readable>)
- **Sections**: <list of sections from dump>
- **Imports**: <list of imports, if any>
- **Exports**: <list of exports, if any>
- **WIT interfaces**: <extracted WIT, components only>
Tool Selection
| Need | Command |
|---|---|
| Validate binary | wasm-tools validate <file> |
| Section layout | wasm-tools dump --skeleton <file> |
| Extract WIT | wasm-tools component wit <file> |
| Print imports/exports | wasm-tools dump --skeleton <file> |
| Find wasm files | Glob **/*.wasm |
| Check file size | ls -la <file> |
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.
- 2mo ago First seen · 59 lines · 25 tokens per session scan A 5bd9619d2dfa
wasm-inspector is an agent published in the GitHub repository vinnie357/claude-skills (27 stars, last pushed 14d ago), licensed MIT. It adds 25 tokens to every session and 628 once invoked, about $0.0001 per session on Opus 5.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-04.
wasm-inspector compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| wasm-inspectorvinnie357/claude-skills | Agent | 27 | 14d ago | MIT | A | 25 | Claude Code |
| review-obsidian-guidelinesuphy/obsidian-reminder | Agent | 662 | 4d ago | MIT | A | 63 | Claude Code |
| debuggerTT-Wang/forge | Agent | 35 | 6d ago | MIT | A | 17 | Claude Code |
| loom-advisorcosmix/loom | Agent | 66 | today | MIT | A | 53 | Claude Code |
| debuggerbostonaholic/rpikit | Agent | 19 | today | MIT | A | 28 | Claude Code |
| evolve-retrospectivemickeyyaya/evolve-loop | Agent | 7 | today | Apache-2.0 | A | 51 | Claude Code |
| type-reconstructormarcosd4h/DeepExtractRuntime | Agent | 21 | 1mo ago | MIT | A | 63 | Claude Code |