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 agentmods add skills/moasq/ios-dev-agent/fix-errornpx skills add moasq/ios-dev-agent --skill fix-errorgit clone --depth 1 https://github.com/moasq/ios-dev-agentWhat 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 | $0.00036 | $0.00825 |
| Opus 5 | $0.00018 | $0.00413 |
| Sonnet 5 | $0.00007 | $0.00165 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
fix-error 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 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.
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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Error
Investigate and resolve unresolved build errors from the error ledger.
Quick Start
- Read
.agents/errors/errors.md— find[UNRESOLVED]entries - If no unresolved entries, check the latest build output for errors
- For each error, follow the resolution workflow below
Resolution Workflow
1. Check History First
Read the error ledger for past [RESOLVED] and [CONSOLIDATED] entries with similar patterns:
- Same file or module?
- Same error type (type mismatch, concurrency, missing reference)?
- Same crash signature?
If a match exists, apply the known fix pattern — don't reinvestigate.
2. Investigate
If no prior match:
- Read the failing file at the reported line
- Read imports, type definitions, related files
- Classify the error by category
- Identify root cause (not just the error message — the actual WHY)
3. Fix
- Edit the failing file(s)
- Fix the root cause, not the symptom
- If multiple files need changes, make all changes before rebuilding
4. Verify
Run the build. If it fails again:
- Is it the same error? (fix didn't work — try another approach)
- Is it a new error? (fix introduced a regression — fix that too)
- Max 3 attempts. If still failing, report findings and stop.
5. Update the Ledger
In .agents/errors/errors.md, change the entry from [UNRESOLVED] to [RESOLVED] and fill in:
## [RESOLVED] <timestamp> — <brief description>
- **Error:** `<error message>`
- **File:** `<file:line>`
- **Category:** `<category from classification>`
- **Symptom:** <what it looked like>
- **Root Cause:** <what actually caused it>
- **Misleading Signal:** <what made this confusing, if applicable>
- **Fix:** <what was changed and why>
- **Files Changed:** <list of modified files>
- **Key Diagnostic:** <the single most important clue>
- **Prevention Rule:** <one-sentence rule that would prevent this>
6. Suggest Consolidation
After resolving, mention: "Run /consolidate-errors to feed this fix back into rules/skills."
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 · 97 lines · 36 tokens per session scan A ce5d0d8b723c
fix-error is a skill published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 825 once invoked, about $0.0002 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
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…