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 HoangNguyen0403/agent-skills-standard --skill incident-hotfixgit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/incident-hotfix)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/incident-hotfix"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/incident-hotfix/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/hoangnguyen0403/agent-skills-standard/incident-hotfix"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/incident-hotfix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.00780 |
| Opus 5.5 | $0.00011 | $0.00312 |
| Sonnet 5.5 | $0.00005 | $0.00156 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
incident-hotfix 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 28d 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Hotfix Skill
[!IMPORTANT] Mitigate a production incident or urgent regression first, then route to root-cause remediation and a postmortem.
Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.
Instructions
When the user asks to perform this workflow, execute the following steps:
Incident Hotfix Workflow
Goal: Stop user-facing harm immediately, then hand off to root-cause discipline instead of debugging live.
Steps
- Triage:
- Severity, blast radius, affected environments/markets, and whether the regression is a rollback candidate.
- Load
deploy-releaserollback path and prior deployment report if present.
- Mitigate first:
- Prefer rollback, feature flag disable, or config revert over a live code fix.
- Confirm mitigation stopped user-facing harm before investigating root cause.
- Do not attempt a root-cause code fix under live production pressure.
- Stabilize:
- Monitor logs, metrics, errors, and core user flows until signals return to baseline.
- Record mitigation timestamp, owner, and evidence.
- Route to remediation:
- Once stable, hand off to
dev-fixfor root-cause debugging under the normal Propose -> Approve -> Verify cycle. - Do not skip
dev-fix's root-cause-before-code requirement just because mitigation already shipped.
- Once stable, hand off to
- Route to learning:
- After
verify-workconfirms the permanent fix, route toretro-learnfor a postmortem. - The confirmed root cause becomes a permanent eval case in the skill or workflow that should have prevented it.
- After
Runtime Contract
- Use only for production incidents or urgent regressions with active user-facing harm; non-urgent bugs go directly to
dev-fix. - Required inputs: incident signal (alert, report, or error spike) plus a mitigation path (rollback, flag, or config revert).
- Return BLOCKED only when no mitigation path exists and the incident cannot be safely stopped.
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.
- 28d ago Changed · +1 lines 61daa37bfc8d
- 1mo ago Changed · -1 lines 39961a03f9a4
- 1mo ago First seen · 82 lines · 27 tokens per session scan A a300e346187b
incident-hotfix is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (582 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 780 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
inspector-workbench
Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit/web-inspector. Don't…
nextjs-idioms
Next.js App Router architecture: React Server Components (RSC), Server Actions, nested layouts, route handlers, and streaming. Use when building or refactoring Next.js web applications. Pair with react-idioms and typescript-idioms.
perf-optimization
Profile-driven performance optimization protocol. Use when profiling data (CPU, heap, trace) is available or when the user requests performance analysis. Covers methodology (Profile → Analyze → Opportunity Scan → Prioritize → Optimize → Benchmark), optimization pattern catalog, safety invariants, and when-to-stop…
incident-response
Structured incident workflow: severity classification, triage, diagnosis, mitigation, postmortem, and prevention. Template-driven with blameless review.
threejs
Build and debug 3D browser apps and games with Three.js or React Three Fiber: scene, materials, lighting, GLTF, physics, character controllers, cameras, post-processing, performance.
debug
Structured bug diagnosis and fixing workflow that reproduces, diagnoses root cause, applies a minimal fix, writes regression tests, and scans for similar patterns.