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.
git clone --depth 1 https://github.com/bernierllc/agents-environment-configWrote 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/rules/bernierllc/agents-environment-config/error-handling)<a href="https://agentmods.dev/rules/bernierllc/agents-environment-config/error-handling"><img src="https://agentmods.dev/badge/rules/bernierllc/agents-environment-config/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/rules/bernierllc/agents-environment-config/error-handling"><img src="https://agentmods.dev/badge/rules/bernierllc/agents-environment-config/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.00440 | $0.00440 |
| Opus 5.5 | $0.00176 | $0.00176 |
| Sonnet 5.5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
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 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
Error Handling
Core Requirements
Zero Error Policy
- Never commit with errors: Always fix issues before committing
- No TypeScript errors:
npm run type-checkmust pass - No linting errors:
npm run lintmust pass - No testing errors: All tests must pass
- Build must succeed:
npm run buildmust complete successfully
Pre-commit Validation
- Use pre-commit hooks to catch errors early
- Run all checks locally before pushing
- Don't rely on CI to catch issues
- Fix errors immediately when they appear
Error Categories
TypeScript Errors
- Compilation errors must be resolved
- Type safety issues must be fixed
- Interface mismatches must be corrected
- Import/export errors must be resolved
Linting Errors
- ESLint violations must be fixed
- Code style issues must be resolved
- Unused variables must be removed
- Import/export consistency must be maintained
Testing Errors
- All unit tests must pass
- Integration tests must pass
- No test failures allowed
- Test coverage requirements must be met
Error Resolution Workflow
- Identify the Error - Read error message carefully, understand root cause
- Fix the Error - Apply minimal fix needed, test locally
- Verify the Fix - Run type-check, lint, test, build
- Commit the Fix - Use conventional commit messages
Quality Gates
Before Every Commit
- TypeScript compilation passes
- Linting passes
- Tests pass
- Build succeeds
- No console errors
References
- Quality Gates: See
topics/quality/gates.mdc - Development Workflow: See
general/development-workflow.mdc - TypeScript: See
languages/typescript/typing-standards.mdc
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 · 64 lines · 440 tokens per session scan A 1f598391aa94
error-handling is a cursor rule published in the GitHub repository bernierllc/agents-environment-config (11 stars, last pushed today), licensed MIT. It adds 440 tokens to every session, about $0.0018 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-31.
Other cursor rules, from other repositories
性能优化方法论
A method for improving program speed by measuring performance first, finding the actual bottleneck, and then checking whether the change helped. Profiling is the process of measuring where a program spends its time or resources.
安全重构
A set of rules for refactoring code, meaning changing its internal structure without changing what it does. It recommends small steps, tests first, extracting functions, and removing repeated code.
error-learning
A rule for recording errors, root-cause analyses, and bug fixes in project notes. RCA means finding the underlying reason a problem happened.
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.