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/consolidate-errorsnpx skills add moasq/ios-dev-agent --skill consolidate-errorsgit 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.00038 | $0.00870 |
| Opus 5 | $0.00019 | $0.00435 |
| Sonnet 5 | $0.00008 | $0.00174 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
consolidate-errors 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consolidate Errors
Analyze resolved errors and update rules/skills to prevent recurrence.
When to Use
Run this after one or more errors have been resolved (marked [RESOLVED] in the error ledger). This skill reads the resolutions, checks what existing rules/skills should have prevented the error, and patches the gap.
Workflow
1. Read Resolved Errors
Read .agents/errors/errors.md
Find entries marked [RESOLVED] (not yet [CONSOLIDATED]).
2. For Each Error, Diagnose the Knowledge Gap
Search existing rules and skills for coverage:
Grep .agents/rules/ for keywords from the error
Grep .agents/skills/ for keywords from the error
Determine which case applies:
| Case | Situation | Action |
|---|---|---|
| A | Rule already covers this exact pattern | No change — mark [CONSOLIDATED] with "coverage sufficient" |
| B | Rule exists but misses this variant | Add the variant to the existing rule |
| C | Skill covers the topic but not this pattern | Add to skill body or create a reference/ file |
| D | Skill exists but description doesn't trigger | Update skill description to include error keywords |
| E | No coverage anywhere | Add to /debugging skill's known crash patterns |
| F | Rules/skills contradict each other | Flag for human review — DO NOT auto-fix |
3. Apply Updates
For each change:
- Read the target file fully before editing
- Make the minimal change — add a warning, extend a table, update keywords
- Never remove existing content
- Trace the change:
<!-- Error ledger: YYYY-MM-DD description -->
4. Update the Ledger
Change [RESOLVED] to [CONSOLIDATED] and add:
- Consolidated To: file path(s) that were updated
- Change Type: Case A/B/C/D/E/F
5. Report
## Consolidation Report
### Processed: [count] resolved errors
| Error | Case | Action | File Updated |
|---|---|---|---|
| [description] | [A-F] | [what was done] | [path or "none"] |
### Coverage Health
- Total errors in ledger: [count]
- Consolidated: [count]
- Unresolved: [count]
- Recurring patterns: [any category appearing 3+ times]
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 · 103 lines · 38 tokens per session scan A 8d69a5fbf282
consolidate-errors is a skill published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 870 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.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…