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 OrcaQubits/agentic-commerce-skills-plugins --skill a2a-error-handlinggit clone --depth 1 https://github.com/OrcaQubits/agentic-commerce-skills-pluginsWrote 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/orcaqubits/agentic-commerce-skills-plugins/a2a-error-handling)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/a2a-error-handling"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/a2a-error-handling/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/orcaqubits/agentic-commerce-skills-plugins/a2a-error-handling"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/a2a-error-handling.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.00049 | $0.01351 |
| Opus 5.5 | $0.00020 | $0.00540 |
| Sonnet 5.5 | $0.00010 | $0.00270 |
| Haiku 4.5 | $0.00005 | $0.00135 |
Grade A, and why
a2a-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 1mo 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A2A Error Handling
Before writing code
Fetch live docs:
- Fetch
https://a2a-protocol.org/latest/specification/for the error handling section - Web-search
site:github.com a2aproject A2A error codesfor error code definitions - Web-search
site:github.com a2aproject a2a-samples errorfor error handling examples - Fetch SDK docs for error classes and exception types
Conceptual Architecture
Error Categories
A2A has three categories of errors:
- JSON-RPC Protocol Errors — Malformed requests, invalid methods, parse failures
- A2A-Specific Errors — Protocol-level issues specific to A2A operations
- Task-Level Failures — The task itself fails during processing (task state →
failed)
JSON-RPC 2.0 Error Format
All errors follow the JSON-RPC 2.0 error response format:
{
"jsonrpc": "2.0",
"id": "request-id",
"error": {
"code": -32600,
"message": "Invalid Request",
"data": { "details": "..." }
}
}
Standard JSON-RPC Error Codes
| Code | Name | Meaning |
|---|---|---|
-32700 |
Parse error | Invalid JSON |
-32600 |
Invalid request | Not a valid JSON-RPC request |
-32601 |
Method not found | Method doesn't exist or isn't supported |
-32602 |
Invalid params | Method parameters are invalid |
-32603 |
Internal error | Server internal error |
A2A-Specific Error Codes
| Code | Name | Meaning |
|---|---|---|
-32001 |
TaskNotFoundError | The referenced taskId doesn't exist |
-32002 |
TaskNotCancelableError | Task is in a state that can't be canceled (terminal state) |
-32003 |
PushNotificationNotSupportedError | Agent doesn't support push notifications |
-32004 |
UnsupportedOperationError | The requested operation is not supported |
-32005 |
ContentTypeNotSupportedError | Client's accepted output modes don't match agent's capabilities |
-32006 |
InvalidAgentResponseError | The agent returned an invalid or malformed response |
-32007 |
ExtendedAgentCardNotConfiguredError | Extended Agent Card is not configured |
-32008 |
ExtensionSupportRequiredError | A required extension is not supported |
-32009 |
VersionNotSupportedError | The requested protocol version is not supported |
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.
- 1mo ago First seen · 122 lines · 49 tokens per session scan A 3323d7368343
a2a-error-handling is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (40 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,351 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
genvm-lint
Validate GenLayer intelligent contracts with the GenVM linter.
archestra-merge-queue
Use when asked to add an Archestra PR to the merge queue, monitor it through merge, or diagnose and repair merge-group CI failures. Own the requested PR until merged or an actionable blocker; opening a PR alone does not start this workflow.
archestra-dev-investigate
Use when investigating Archestra bugs or incidents — staging issues, backend 50x errors, Drizzle failed queries, DB connection pressure, deploy regressions, or Kubernetes/runtime symptoms. Orientation only; defers the process to /investigate.
ironmesh-peers
Drill into per-peer IronMesh metrics — retry reasons, session rekeys, offline-since, transport type. Use when ironmesh-status shows a problem on a specific peer and you need detail.
metengine-data-agent
Real-time smart money analytics API for Polymarket prediction markets, Hyperliquid perpetual futures, and Meteora Solana LP/AMM pools. 63 endpoints. Pay-per-request via x402 on Solana Mainnet USDC. No API keys.
internet-court
Entry point for Internet Court — the trust layer for agent-to-agent commerce. Use whenever an agent needs to transact with another agent or a paid service, or a user mentions agent payments, paid APIs (HTTP 402/x402), wallet custody or trust concerns, spending mandates, delegated permissions (ERC-7710/7715), escrow…