Wasm Module Inspect
Inspect a compiled .wasm binary — validates structure, lists exports and imports, detects SIMD and threading opcodes, and reports binary size. Requires wabt; wasm-opt (Binaryen) is optional.
Install
$ agentstack add skill-gertsylvest-meta-team-wasm-module-inspect ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-gertsylvest-meta-team-wasm-module-inspect) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
WASM Module Inspect
Inspect a compiled .wasm binary to verify it is valid, understand its public API surface, and detect compilation features (SIMD, threads).
Requirements
- wabt (
wasm-validate,wasm2wat) — install viabrew install wabt(macOS),apt install wabt(Linux), or from https://github.com/WebAssembly/wabt/releases - wasm-opt (optional, Binaryen) — install via
brew install binaryenfor feature reporting
Instructions
The argument is in $ARGUMENTS. Pass it directly to the inspection script:
bash "$(dirname "$0")/inspect.sh" $ARGUMENTSOutput sections
| Section | What it reports | |---|---| | SIZE | Binary size in bytes and KB | | VALID | Pass/fail from wasm-validate | | EXPORTS | All exported functions, memories, tables, globals | | IMPORTS | All imported functions (JS host functions the module depends on) | | SIMD | Whether v128 (WASM SIMD) opcodes are present | | THREADS | Whether atomic instructions are present (requires SharedArrayBuffer) | | FEATURES | Full feature list from wasm-opt --print-features (if available) |
Typical usage
# After an Emscripten build — confirm exports match expected API
bash inspect.sh build/my-dsp.wasm
# Before deploying — confirm SIMD is present in the optimised build
bash inspect.sh dist/processor.wasmWhat to look for
- Exports should be minimal — only the functions the JS/worklet layer calls (e.g.
_init,_process,_destroy). Unexpected exports indicate-s EXPORTED_FUNCTIONSwas not set correctly. - SIMD present confirms
-msimd128was applied and the WASM binary actually contains vectorised code. - Threads present means the page must be served with
COOP/COEPheaders — flag this if the deployment environment does not support them. - Large binary size may indicate the Emscripten filesystem (
-s FILESYSTEM=0not set) or C++ RTTI/exceptions were not disabled.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: gertsylvest
- Source: gertsylvest/meta-team
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.