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 charlieviettq/awesome-agent-skill --skill cross-platform-error-handlinggit clone --depth 1 https://github.com/charlieviettq/awesome-agent-skillWrote 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/charlieviettq/awesome-agent-skill/cross-platform-error-handling)<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/cross-platform-error-handling"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/cross-platform-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/charlieviettq/awesome-agent-skill/cross-platform-error-handling"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/cross-platform-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.00031 | $0.00365 |
| Opus 5.5 | $0.00012 | $0.00146 |
| Sonnet 5.5 | $0.00006 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
cross-platform-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.
What it actually says
Cross-Platform Error Handling
Patterns for centralized error capture, user-appropriate messaging, and observability across web and mobile clients.
When to use
- Inconsistent error UX across platforms
- Unhandled promise rejections or crash reports
- Adding global error boundary/handler
When not to use
- Server-side API error design (use
api-and-interface-design) - Single-platform app with existing mature pattern (extend, don't rewrite)
Architecture
Error occurs → classify (network/auth/validation/unknown)
→ log (structured, no PII)
→ user message (actionable, localized)
→ optional retry/report
Platform patterns
| Platform | Mechanism |
|---|---|
| React web | Error boundary + window unhandledrejection |
| React Native | Global handler + native crash reporting SDK |
| Next.js | error.tsx boundaries + server action error mapping |
User messaging rules
- Network — "Check connection" + retry
- Auth — redirect to login; no token details
- Validation — field-level hints
- Unknown — generic message + support/ref ID; log details server-side
Checklist
- Central error type taxonomy (shared package if monorepo)
- No stack traces shown to end users
- Correlation ID in user-facing error when support needed
- Regression test for at least one error path per platform
- Offline mode handled where applicable
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 · 53 lines · 31 tokens per session scan A a74f679d0aa5
cross-platform-error-handling is a skill published in the GitHub repository charlieviettq/awesome-agent-skill (26 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 365 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
tool-calling-tutor
Use when a tool-calling agent does not call a tool, sends wrong arguments, loops without stopping, or needs a function schema. Guides a four-branch diagnosis and five-step schema repair. Do not use for framework-specific, MCP-server, or production-observability questions.
error-translator
A Chinese-language assistant that translates English programming errors and explains what they mean. It covers common errors from languages and frameworks including Python, JavaScript, TypeScript, Java, and others.
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
eslint-fix
A project-aware assistant for finding and fixing ESLint errors, warnings, and configuration compatibility problems. ESLint is a tool that checks JavaScript and TypeScript code for style and common mistakes.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.
seedance-debugger
A troubleshooting guide for fixing common problems in Seedance 2.0 AI-generated videos, such as changing faces, unwanted text, watermarks, style changes, or broken scene transitions.