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 wasix-org/wasinix --skill wasix-bug-triagegit clone --depth 1 https://github.com/wasix-org/wasinixWrote 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/wasix-org/wasinix/wasix-bug-triage)<a href="https://agentmods.dev/skills/wasix-org/wasinix/wasix-bug-triage"><img src="https://agentmods.dev/badge/skills/wasix-org/wasinix/wasix-bug-triage/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/wasix-org/wasinix/wasix-bug-triage"><img src="https://agentmods.dev/badge/skills/wasix-org/wasinix/wasix-bug-triage.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.00056 | $0.00248 |
| Opus 5 | $0.00028 | $0.00124 |
| Sonnet 5 | $0.00011 | $0.00050 |
| Haiku 4.5 | $0.00006 | $0.00025 |
Grade A, and why
wasix-bug-triage 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.
What it actually says
WASIX bug triage
Read AGENTS.md, docs/style.md, docs/building.md, docs/spot.md, and the
relevant package or language documentation. Search WASIX-TODO.md before
treating a workaround as a new bug.
Inventory patches, disabled tests, broken declarations, and observed failures.
Group structurally identical symptoms, identify the likely owner, and reduce
each candidate from a real failing package to the smallest reproducer that still
fails under Wasmer. Use Spot for inexpensive experiments, then distinguish its
evidence from final verification.
Do not edit shipping code, mark work broken, disable tests, open issues, or contact upstream unless explicitly requested. Report each reproducer, the exact failure, affected scope, existing tracking, likely owning layer, and the next discriminating experiment.
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 · 26 lines · 56 tokens per session scan A 39f8b8a83f69
wasix-bug-triage is a skill published in the GitHub repository wasix-org/wasinix (6 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 248 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
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
work
Deliver one maintainer-approved EmDash issue, choosing the bug-fix path for a defect and the direct implementation path for an enhancement or task.