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 stfade/moth --skill moth-debug-first-fixgit clone --depth 1 https://github.com/stfade/mothWrote 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/stfade/moth/moth-debug-first-fix)<a href="https://agentmods.dev/skills/stfade/moth/moth-debug-first-fix"><img src="https://agentmods.dev/badge/skills/stfade/moth/moth-debug-first-fix/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/stfade/moth/moth-debug-first-fix"><img src="https://agentmods.dev/badge/skills/stfade/moth/moth-debug-first-fix.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.00064 | $0.00338 |
| Opus 5.5 | $0.00026 | $0.00135 |
| Sonnet 5.5 | $0.00013 | $0.00068 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
moth-debug-first-fix 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 1mo 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
Moth Debug First Fix
Workflow
- Capture the exact failing command, error output, package context, and the smallest relevant file excerpts.
- Redact secrets before storing, quoting, or sending the error anywhere.
- Call
analyze_errorwhen available. Treat itslikely_cause,best_first_fix,avoid, andconfidenceas a starting brief, not certainty. - If context is missing, gather only the narrow missing context named by the brief.
- Patch the smallest code surface that explains the key error line.
- Follow the verified memory lifecycle:
analyze_error-> apply/attempt fix -> run verification command -> callremember_fix_resultwithverification_commandandverification_result. - Call
remember_fix_resultonly when a fix/change was actually attempted, the verification command was actually run, and the result is unambiguouslypassedorfailed.
Guardrails
- Do not start with a broad refactor.
- Do not scan the whole repository unless the user explicitly asks.
- Do not treat Moth confidence as proof.
- Do not call
remember_fix_resultfor suggestions, unapplied changes, skipped changes, missing verification, ambiguous results, or guesses. - Do not record full sensitive logs in memory.
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.
- 1mo ago First seen · 25 lines · 64 tokens per session scan A aa7a6f544bbb
moth-debug-first-fix is a skill published in the GitHub repository stfade/moth (2 stars, last pushed 5mo ago), licensed MIT. It adds 64 tokens to every session and 338 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
report-issue-local
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…
opik-explain
Root-cause a specific Opik trace, or a pattern across traces, and return a grounded explanation. Uses the hosted Opik MCP when it is connected, and falls back to SDK scripting otherwise. Returns the root cause, the evidence spans as clickable Opik UI links, and one suggested next step. Use for "why did this trace…
isuzu-unity-cli
Drive the open Unity Editor from the shell with the isuzu-unity-cli command: console errors, compiling and tests, scenes, GameObjects and components, prefabs, play mode, uGUI clicks, and C# run inside the Editor. SKILL.md gives a command for each common task, so no tool list is needed.
push-notification-tester
Test VoIP push notifications for Telnyx WebRTC iOS (APNs) and Android (FCM) apps. Use when debugging push notification delivery, validating certificate/credential setup, or testing that a device receives VoIP pushes correctly.
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.