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 Eliyce/paqad-ai --skill error-catalog-maintainergit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/eliyce/paqad-ai/error-catalog-maintainer)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/error-catalog-maintainer"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/error-catalog-maintainer/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/eliyce/paqad-ai/error-catalog-maintainer"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/error-catalog-maintainer.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.00012 | $0.00583 |
| Opus 5 | $0.00006 | $0.00292 |
| Sonnet 5 | $0.00002 | $0.00117 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
error-catalog-maintainer 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 10d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What It Does
Maintains per-module error catalogs so new or changed failure paths are documented with recovery guidance, ownership signals, and registry consistency.
Use This When
Use this when a change introduces new error codes, modifies user-facing messages, or changes the recovery path for existing failures.
Inputs
- Read the module
error-catalog.mdand any API error docs first. - Read the changed implementation and any available error-code extraction output.
- Read
references/error-entry-fields.mdbefore editing catalog entries.
Procedure
- Run
scripts/find-error-catalogs.shto locate canonical per-module error catalogs. - Run
scripts/extract-error-codes.sh <changed-files...>to surface candidate codes the diff introduces or renames. - For each new / changed code, write or update its entry using
assets/entry.template.md(code, trigger, user message, operator meaning, recovery, retry safety, ownership). - Check global registry / module prefix collisions explicitly.
- Format report per
assets/output.template.mdand validate withscripts/lint-output.sh. Vague user messages or unknown recovery →## Catalog Gaps, never a completed entry.
Output Contract
- Match
assets/output.template.md:## Updated Error Entriesand## Catalog Gaps. - Every updated entry must name the error code, catalog path, and changed trigger, message, recovery, or ownership field.
- Output must pass
scripts/lint-output.sh(exit 0). - Unknown recovery guidance, owner, or retry safety belongs under
Catalog Gaps, never as a guessed completed entry.
Escalate / Stop Conditions
- Ask when the correct user-facing recovery guidance depends on product or support policy.
- Warn when an error path leaks internal details or has no documented operator response.
- Do not approve an entry that only says a generic failure occurred.
Resources
references/error-entry-fields.mdscripts/find-error-catalogs.shscripts/extract-error-codes.shscripts/lint-output.shassets/output.template.mdassets/entry.template.mdruntime/templates/runner-scripts/extract-error-codes.sh.hbsagents/openai.yaml
What ships with it
7 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.
- 10d ago First seen · 69 lines · 12 tokens per session scan A cbe8b5277d23
error-catalog-maintainer is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 583 once invoked, about $0.0001 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
pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer…
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
auto-go
A command that implements code from a SPEC, a document describing the required behavior and work.
auto-plan
A code-planning skill that examines a codebase and creates a detailed specification, implementation plan, and acceptance criteria. It can organize requirements using EARS, a structured way to describe how software should behave in different situations.
agent-pipeline
Multi-agent pipeline orchestration skill.
adaptive-quality
Per-task execution profile selection based on complexity in Balanced quality mode.