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 Jkudjo/oh-my-cursor --skill incidentgit clone --depth 1 https://github.com/Jkudjo/oh-my-cursorWrote 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/jkudjo/oh-my-cursor/incident)<a href="https://agentmods.dev/skills/jkudjo/oh-my-cursor/incident"><img src="https://agentmods.dev/badge/skills/jkudjo/oh-my-cursor/incident/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/jkudjo/oh-my-cursor/incident"><img src="https://agentmods.dev/badge/skills/jkudjo/oh-my-cursor/incident.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.00018 | $0.00290 |
| Opus 5 | $0.00009 | $0.00145 |
| Sonnet 5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
incident 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 9d 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
incident
Full production incident response protocol. Handles the furnace scenarios — green metrics but users affected, regional failures, post-deploy regressions.
Phases
- Impact triage — scope, symptom, start time, blast radius (2 min)
- Evidence gathering — read-only: recent changes, error logs, traces, infra health, dependencies, regional scope
- Hypothesis tree — app, infra, data, client/observability — full tree before investigating any branch
- Safe remediation — root cause confirmed → state blast radius + rollback → fix → verify
- Incident record — timeline, root cause, fix, monitoring gap, follow-up
Hard rules
- Read-only until cause is confirmed
- Green metrics ≠ no incident — metrics lie via wrong thresholds, aggregation, wrong segment
- "The deploy caused it" is a hypothesis, not a fact
- No destructive infra changes without explicit confirmation + rollback plan
- No disabling auth during incident response
Example
@incident "intermittent 503s in us-east after today's deploy — pods Running, CPU/memory normal"
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.
- 9d ago First seen · 29 lines · 18 tokens per session scan A 06cec830adc6
incident is a skill published in the GitHub repository Jkudjo/oh-my-cursor (1 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 290 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 skills, from other repositories
systematic-debugging
Use when encountering bugs, test failures, unexpected behavior, or any technical issue before proposing fixes.
firebase-crashlytics
Use when implementing crash reporting, capturing fatal/non-fatal errors, recording isolate/async exceptions, customizing reports, or uploading obfuscated symbols.
flutter-errors
Use when hitting layout errors (RenderFlex overflow, unbounded constraints, RenderBox not laid out), scroll errors, or setState-during-build errors.
cause-and-effect
Systematic Fishbone analysis exploring problem causes across six categories.
why
Iterative Five Whys root cause analysis drilling from symptoms to fundamentals.
audit-performance
Audit runtime performance (CWV, load priority). Use when "slow page", "LCP/INP/CLS", "fetchpriority", "early hints", "speculation rules", "bfcache", or "long tasks". JS payload → audit-bundle-size. Instant nav implement → enhance-web-instant-nav. Breaking point → test-load.