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 aeonfun/aeon --skill skill-repairgit clone --depth 1 https://github.com/aeonfun/aeonWrote 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/aeonfun/aeon/skill-repair)<a href="https://agentmods.dev/skills/aeonfun/aeon/skill-repair"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/skill-repair.svg" alt="Measured on agentmods" 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.00028 | $0.04064 |
| Opus 5 | $0.00014 | $0.02032 |
| Sonnet 5 | $0.00006 | $0.00813 |
| Haiku 4.5 | $0.00003 | $0.00406 |
Grade A, and why
skill-repair scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`gh` and `git` handle auth internally, so the diagnostic reads carry no `$SECRET` on the command line. There is no network sandbox — `curl` works; use `gh api` for GitHub reads, and prefer **WebFetch** over `curl` for an Copies of this mod
2 near-identical copies found in the catalogue:
- skill-repair — 100% identical, 0 lines differ
- skill-repair — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — Skill name to repair. If empty, runs systemic triage and picks the worst fixable target.
${var}modifiers: prefixdry-run:to diagnose only without writing a PR (e.g.dry-run:digest).
Today is ${today}. Your task is to diagnose and repair the worst-impact failing or degraded skill — preferring a single shared fix over N per-skill patches when failures cluster.
Phases
PREFLIGHT → TRIAGE → DIAGNOSE → REPAIR → VERIFY → LOG
Stop early at the appropriate exit code if any phase finds nothing actionable.
Exit taxonomy
Pick exactly one before notifying.
| Code | Meaning |
|---|---|
REPAIR_OK_FIXED |
Per-skill fix applied, PR opened |
REPAIR_OK_SYSTEMIC |
Shared root cause across N skills — single shared fix or shared issue filed |
REPAIR_DIAGNOSED_NO_FIX |
Root cause known but requires operator action (e.g. missing secret, upstream API down). Issue updated, no PR |
REPAIR_NO_TARGETS |
All tracked skills healthy and no open fixable issues |
REPAIR_DRY_RUN |
var=dry-run:NAME — diagnostic only, no PR |
REPAIR_BLOCKED |
Preflight failed (gh auth, missing files) or cooldown active |
1. PREFLIGHT
Bail early with REPAIR_BLOCKED (and notify with the reason) if any of these fails:
gh auth statussucceeds.memory/cron-state.jsonexists and parses as JSON.memory/issues/INDEX.mdexists. If absent, bootstrap a minimal one (Open + Resolved tables, no rows).memory/state/skill-repair-history.jsonexists. If absent, create{}.
Cooldown / idempotency (skip target with REPAIR_BLOCKED if any matches; don't loop on a fix that didn't take):
- The chosen target appears in
memory/state/skill-repair-history.jsonwithlast_repair_atwithin 24h. (Operator can override by deleting the entry.) - An open PR already exists matching
fix/skill-repair-{name}-*—gh pr list --state open --search "head:fix/skill-repair-{name}". - More than 3 skill-repair PRs already opened in the current UTC day — rate-limit our own PRs.
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.
- 2d ago First seen · 266 lines · 28 tokens per session scan A 25d7ec4b7c05
skill-repair is a skill published in the GitHub repository aeonfun/aeon (716 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 4,064 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
skill-audit
Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review. Use when: AUTOMATICALLY ACTIVATE when user requests auditing:. "audit and check the entire app". "audit X for Y" or "check for broken features".
debugging-strategies
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
parallel-debugging
Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration. Use this skill when debugging bugs with multiple potential causes, performing root cause analysis, or organizing parallel investigation workflows.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
error-handling-patterns
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.