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/saidsef/mcp-github-pr-issue-analyser/error-handlingnpx skills add saidsef/mcp-github-pr-issue-analyser --skill error-handlinggit clone --depth 1 https://github.com/saidsef/mcp-github-pr-issue-analyserWrote 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/saidsef/mcp-github-pr-issue-analyser/error-handling)<a href="https://agentmods.dev/skills/saidsef/mcp-github-pr-issue-analyser/error-handling"><img src="https://agentmods.dev/badge/skills/saidsef/mcp-github-pr-issue-analyser/error-handling.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 | $0.00019 | $0.01622 |
| Opus 5 | $0.00010 | $0.00811 |
| Sonnet 5 | $0.00004 | $0.00324 |
| Haiku 4.5 | $0.00002 | $0.00162 |
Grade A, and why
error-handling 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 yesterday.
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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Handling
Every tool in this server fails through one small set of typed errors. The code in the message tells you which of the three responses is right: back off, correct the call, or stop and tell the user.
Reading an Error
Failures arrive as a ToolError whose message opens with a bracketed code:
[NOT_FOUND] HTTP 404: PR #4321: Resource not found GitHub said: Not Found
The prefix is [<CODE>] HTTP <status>: when a status is known and [<CODE>]
when it is not. Read the code first, since the prose after it varies with the
call and is not stable enough to match on.
What follows the prefix has three parts. The call that failed comes first, such
as PR #4321. The server's own reading of the status comes next. Whatever
GitHub said about the refusal comes last, after GitHub said: , and a 422
appends its field-level errors as <field>: <message> after that. The last part
is absent when GitHub sent no body or sent one that is not JSON.
Report the GitHub said text to the user, since it names the cause where the
codes only name the class.
The GraphQL-backed tools wrap failures once more, so their messages read
[GITHUB_API_ERROR] Failed to <action>: <original error>. The action names the
step that failed, such as fetch user activities or fetch status checks. A
missing resource is the exception and keeps its own NOT_FOUND code rather
than being re-wrapped.
The Codes
| Code | Status | Means | Do |
|---|---|---|---|
AUTH_FAILED |
401 | The token is missing, expired or revoked | Stop. Tell the user to re-authenticate. Retrying cannot help |
RATE_LIMITED |
403 | The primary or the secondary rate limit is exhausted | Wait for the reset, then retry the same call unchanged |
NOT_FOUND |
404 | The resource is absent, or the token cannot see it | Check the owner, repo and number. Do not retry unchanged |
VALIDATION_ERROR |
422 | GitHub rejected the arguments | Fix the arguments. Retrying unchanged fails again |
GITHUB_API_ERROR |
403 or other | Permission denied, or any status not listed above | Read the message. Permission problems need a token or approval change, not a retry |
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.
- yesterday Changed · +27 lines 90234e7309b0
- 5d ago First seen · 104 lines · 19 tokens per session scan A 3d63b9c86376
error-handling is a skill published in the GitHub repository saidsef/mcp-github-pr-issue-analyser (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,622 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
atelier
Two-agent post-generation quality gate for vibe-coded applications. Deterministic, gradeable ruleset enforcing UI/UX design-system craft and backend architectural soundness.
mcp-dino
Skill "mcp-dino" from shennawardana23/mcp-dino, covering skill.md — dino-mcp development skills, skill: build & run, quick build (go only, uses existing ui), full build (vite ui + go) and run in dev mode (verbose).
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
amazon aurora dsql
Deprecated compatibility redirect for Aurora DSQL guidance. Use when a request concerns DSQL, Aurora DSQL, distributed SQL, DSQL schemas, migrations, queries, authentication, performance, or application development.
resolve-pr-comments-stack
Resolve unresolved PR review comments across an entire Graphite (gt) stack of many PRs, bottom-up, in one working directory. Use when asked to "go through this stack and resolve comments", "clean up review comments across the whole stack", or given a list/range of PR numbers that form (or partially form) a gt stack.…
split-commit-into-stack
Split one oversized commit or branch into a stack of independently reviewable Graphite (gt) PRs - deciding what genuinely separates, what is atomic and must stay whole, and proving each lower PR builds and passes without the ones above it. Use when asked to "split this PR", "this commit is too big", "break this into a…