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 gertsylvest/meta-team --skill emscripten-env-auditgit clone --depth 1 https://github.com/gertsylvest/meta-teamWrote 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/emscripten-env-audit)<a href="https://agentmods.dev/skills/gertsylvest/meta-team/emscripten-env-audit"><img src="https://agentmods.dev/badge/skills/gertsylvest/meta-team/emscripten-env-audit/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/emscripten-env-audit"><img src="https://agentmods.dev/badge/skills/gertsylvest/meta-team/emscripten-env-audit.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.00065 | $0.01343 |
| Opus 5 | $0.00032 | $0.00672 |
| Sonnet 5 | $0.00013 | $0.00269 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
emscripten-env-audit 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 10d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Emscripten Environment Audit
Parse Emscripten build flags and flag configuration patterns that cause runtime failures in AudioWorkletGlobalScope. Designed to catch the class of errors that require a full browser session to surface otherwise — self is not defined, fetch is not a function, registerProcessor not called — before any code is written or rebuilt.
This skill encodes the compatibility research that took ~3–4 hours of iterative debugging in Sprint 5 of faust-poc1. A 30-minute research session reading the Emscripten GitHub issues and MDN AudioWorkletGlobalScope docs would have identified all five failure modes before the first make synth-wasm.
Requirements
- Python 3.8+ (for the audit script)
- The Makefile or shell script containing the
emccinvocation
Instructions
Arguments are in $ARGUMENTS. Pass them directly to the audit script:
python3 "$(dirname "$0")/audit.py" $ARGUMENTS
Checks performed
| Check | Severity | Pattern detected |
|---|---|---|
MODULARIZE=1 |
ERROR | Wraps --post-js content inside the factory function body. registerProcessor() never executes at top level. |
ENVIRONMENT=web or ENVIRONMENT=node |
ERROR | Wrong environment for a worklet target. Emscripten will emit DOM access code or Node.js-specific code. |
No --pre-js with self polyfill |
WARN | ENVIRONMENT=worker assumes self is defined. AudioWorkletGlobalScope does not expose it. |
No --pre-js with self.location polyfill |
WARN | Emscripten reads self.location.href for WASM path resolution. Absent in worklet scope. |
No instantiateWasm hook pattern |
WARN | Emscripten's default WASM loading calls fetch(). fetch is unavailable in AudioWorkletGlobalScope. |
ALLOW_MEMORY_GROWTH=1 without buffer re-read note |
INFO | HEAPF32.buffer is invalidated on memory growth. Safe if HEAPF32.buffer is re-read on each process() call. |
EXPORT_NAME without MODULARIZE |
INFO | EXPORT_NAME is only meaningful with MODULARIZE=1. Has no effect without it. |
Missing --pre-js or --post-js for worklet target |
WARN | Both are typically needed: --pre-js for polyfills, --post-js to bundle the AudioWorkletProcessor class. |
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.
- 10d ago First seen · 86 lines · 65 tokens per session scan A b0655a7a183e
emscripten-env-audit is a skill published in the GitHub repository gertsylvest/meta-team (5 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 1,343 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.