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 rules/apisec-inc/apisec-skills/error-sanitizationgit clone --depth 1 https://github.com/apisec-inc/apisec-skillsWhat 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.00197 | $0.00197 |
| Opus 5 | $0.00098 | $0.00098 |
| Sonnet 5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
error-sanitization 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 2d 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 sanitization rule
API error responses must never include stack traces, internal field names, database error messages, ORM errors, or any internal system detail.
Never generate error handlers that return err.message, error.stack, or raw exception objects directly to the client.
Insecure pattern to refuse: res.status(500).json({ error: err.message })
Safe pattern to generate instead: res.status(500).json({ error: 'Internal server error', requestId: req.id })
Always generate a generic user-facing message plus a unique request/correlation ID for internal tracing. The requestId allows ops teams to find the real error in logs without exposing it to clients.
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.
- 2d ago First seen · 25 lines · 197 tokens per session scan A 07f6fdedd854
error-sanitization is a cursor rule published in the GitHub repository apisec-inc/apisec-skills (18 stars, last pushed 5mo ago), licensed MIT. It adds 197 tokens to every session, about $0.0010 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-30.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.