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 commands/emaraschio/cursor-commands/add-error-handlinggit clone --depth 1 https://github.com/emaraschio/cursor-commandsWrote 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/commands/emaraschio/cursor-commands/add-error-handling)<a href="https://agentmods.dev/commands/emaraschio/cursor-commands/add-error-handling"><img src="https://agentmods.dev/badge/commands/emaraschio/cursor-commands/add-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.1 | $0.00013 | $0.00413 |
| Opus 5 | $0.00006 | $0.00206 |
| Sonnet 5 | $0.00003 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
add-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 5d 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
Overview
Add consistent error handling to the targeted code. Full workflow: .cursor/skill-contracts/add-error-handling/SKILL.md (user install: ~/.cursor/skill-contracts/add-error-handling/SKILL.md).
Defaults
None. See skill for workflow defaults.
Steps
- Read
.cursor/skill-contracts/add-error-handling/SKILL.mdfor the full agent contract; if that file is missing, read~/.cursor/skill-contracts/add-error-handling/SKILL.md. - Execute the workflow in order; do not skip safety steps.
- Report outcomes per skill (summary, tables, or checklist as specified).
Anti-patterns
- Never swallow an error silently. Trigger: catching an exception you cannot fully handle. Wrong: an empty catch block, or one that hides the failure with no log or rethrow. Correct: handle it meaningfully, or log and rethrow so the failure stays visible. Reason: swallowed errors turn real failures into silent data loss and undebuggable behavior.
- Do not wrap everything in try/catch. Trigger: deciding where to add error handling. Wrong: blanket try/catch on every call and layer regardless of risk. Correct: handle errors at meaningful boundaries where you can recover or report. Reason: excessive handling buries the happy path and masks where failures truly originate.
Examples
/add-error-handling
Maintainers
Behavioral eval: .cursor/skill-contracts/add-error-handling/eval/cases.md. Ship gate sections: A, S before changing SKILL.md or this command.
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.
- 5d ago First seen · 38 lines · 13 tokens per session scan A cb40ae422ea7
add-error-handling is a command published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 29d ago), licensed MIT. It adds 13 tokens to every session and 413 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 commands, from other repositories
grok_init
Discover, verify, and persist the local HTTP proxy used by Grok Build Supervisor.
analyze-deps
Analyze the project's dependency tree, identify unused or duplicate dependencies, and suggest optimizations.
code-review
Review the code changes in this conversation (or the files I've @-mentioned) systematically.
security-audit
Perform a security-focused review of the code I've @-mentioned (or the most relevant changes in this conversation).
run-tests-and-fix
Run the project's test suite, fix any failures, and report what changed.
update-deps
Update the project's dependencies and ensure the project still works.