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 New1Direction/korgex --skill incident-responsegit clone --depth 1 https://github.com/New1Direction/korgexWrote 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/new1direction/korgex/incident-response)<a href="https://agentmods.dev/skills/new1direction/korgex/incident-response"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/incident-response.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.00018 | $0.00327 |
| Opus 5 | $0.00009 | $0.00163 |
| Sonnet 5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
incident-response 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 7d 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
In an incident the priority order is: restore service → understand cause → prevent recurrence. Don't invert it by debugging a live outage while users suffer.
- Mitigate first. Reduce impact NOW: roll back the recent deploy, flip the feature flag off, fail over, scale up, or shed load. The fastest safe path to "users are OK again" beats the elegant fix.
- Stabilize, then investigate. Once impact is contained, you have room to find the real cause without the clock running.
- Use your signals. Logs, metrics, traces, recent changes (a deploy/config change right before the incident is the prime suspect). Form one hypothesis at a time (see systematic-debugging).
- Communicate. State what's impacted, what you're doing, and the next update time. Silence is worse than bad news.
- Fix the root cause with a regression test, and only then re-enable / re-deploy.
- Blameless post-mortem. Write up the timeline, root cause, and concrete action items to prevent recurrence (better alerting, a guard, a test). Focus on the system and process, not who.
Red flag: forward-fixing a live outage instead of rolling back; declaring it resolved without confirming recovery in the metrics.
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.
- 7d ago First seen · 28 lines · 18 tokens per session scan A 82318be3472a
incident-response is a skill published in the GitHub repository New1Direction/korgex (5 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 327 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
cce-routing
Use Cursor Bridge's read-only cursorcontextengine for unfamiliar project understanding when the exact code location is unknown or the task requires tracing behavior, symbols, callers and callees, data flow, registrations, interface implementations, ownership boundaries, or cross-module relationships. Trigger for…
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions. Use the GitHub app from this plugin for PR metadata and patch context, and use gh for Actions check and log inspection before implementing any approved fix.
sentry
Query Sentry organizations, projects, and unresolved issues/errors via the Sentry API. Use when the user asks about Sentry errors, issues, or projects.
signoz
Query observability (services, traces, logs, metrics) from a SigNoz instance via its API. Use when the user asks about app performance, errors, latency, or telemetry in SigNoz.
rel-ai-debugging
Use when repository behavior is reproducibly wrong and needs causal diagnosis or repair, including errors, broken tests, crashes, regressions, failed contracts, or incorrect runtime behavior. Do not use for general audits or final verification when no active defect is being diagnosed.
rel-ai-investigation
Use for read-only repository questions that need evidence, including architecture audits, feasibility studies, dependency or caller tracing, impact analysis, implementation-status checks, and proof of how something works. Do not use to implement fixes or for final completion or release verification of changes already…