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 peteromallet/Arnold --skill fix-the-fixergit clone --depth 1 https://github.com/peteromallet/ArnoldWrote 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/peteromallet/arnold/fix-the-fixer)<a href="https://agentmods.dev/skills/peteromallet/arnold/fix-the-fixer"><img src="https://agentmods.dev/badge/skills/peteromallet/arnold/fix-the-fixer/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/peteromallet/arnold/fix-the-fixer"><img src="https://agentmods.dev/badge/skills/peteromallet/arnold/fix-the-fixer.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.00097 | $0.01106 |
| Opus 5.5 | $0.00039 | $0.00442 |
| Sonnet 5.5 | $0.00019 | $0.00221 |
| Haiku 4.5 | $0.00010 | $0.00111 |
Grade A, and why
fix-the-fixer 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix the fixer
Repair the repair system, not the epic symptom. Keep the failed fixer and the meta-fixer as distinct processes so the repair has independent custody and cannot certify itself.
Invoke
Require one non-empty text flag:
$fix-the-fixer --target "custody-control-plane-20260714 / m6-exact-contract-and-20260716-1303"
Render the implementation goal before launch:
python "<skill-dir>/scripts/render_goal.py" --target "<epic/session text>"
Reject an absent or blank --target. Preserve the text exactly as target
orientation; require the agent to resolve canonical IDs and current state from
durable evidence rather than treating the flag as proof.
Compose the existing guidance
Read and apply ../superfixer-debug/SKILL.md for the custody walk, four axes,
failure shapes, sibling hunt, and close-the-loop method. When the target is a
cloud session, also use $megaplan-cloud for supported status and repair
transport. This skill overrides superfixer-debug only in these ways:
- Launch exactly one implementation/recovery agent. Do not fan out or let that agent delegate further agents.
- Use the current authorization envelope. Never infer push, deployment, restart, broad process control, or direct epic-state mutation authority from the desire to recover the epic.
- Prefer the current supported resident/cloud commands and receipts over old literal host, branch, wrapper-copy, or process commands in historical text.
Read historical-runs.md when selecting prompt language, proof gates, or precedent. It separates raw artifacts from inference.
Launch one durable meta-fixer
Use the resident-managed launch boundary when available. It preserves the origin envelope, manifest, full log, result, target ref, delivery ownership, and restart-safe continuation. Pass the rendered goal as the task; classify it as execution, git-backed when source repair is possible, and D8-D10/high. Preserve the caller's existing synthesis/delivery role instead of inventing a second user-facing owner.
What ships with it
3 files 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.
- 1mo ago First seen · 103 lines · 97 tokens per session scan A 9740f2def4fe
fix-the-fixer is a skill published in the GitHub repository peteromallet/Arnold (98 stars, last pushed yesterday), licensed Apache-2.0. It adds 97 tokens to every session and 1,106 once invoked, about $0.0004 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.
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.
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…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.