incident-hotfix

incident-hotfix is a command for GitHub Copilot from HoangNguyen0403/agent-skills-standard. It costs 23 tokens per session (578 once invoked), scanned A, original, MIT.

An incident-response workflow for stopping harm from a production failure or urgent regression. A production incident is a serious problem affecting users in the live system; the workflow separates immediate mitigation from later root-cause repair.

In plain words
What is it for?
Use it to assess severity and impact, roll back or disable the failing change, confirm recovery, and hand the issue to normal debugging and post-incident learning.
Why use it?
It reduces ongoing user impact without encouraging risky debugging or code changes while the live incident is still unfolding.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt.

Good fit Use it to assess severity and impact, roll back or disable the failing change, confirm recovery, and hand the issue to normal debugging and post-incident learning.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/hoangnguyen0403/agent-skills-standard/incident-hotfix
Install

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.

Clone the repo
git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for incident-hotfix

README.md
[![agentmods](https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/incident-hotfix/github.svg)](https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/incident-hotfix)
Your own site
<a href="https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/incident-hotfix"><img src="https://agentmods.dev/badge/commands/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.

agentmods 80×15 button for incident-hotfix

Your own site · 80×15
<a href="https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/incident-hotfix"><img src="https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/incident-hotfix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 578 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00578
Opus 5 $0.00012 $0.00289
Sonnet 5 $0.00005 $0.00116
Haiku 4.5 $0.00002 $0.00058

Measured 6d ago against content hash a3454a24769e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 6d 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.

.github/prompts/incident-hotfix.prompt.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Incident Hotfix Workflow

Goal: Stop user-facing harm immediately, then hand off to root-cause discipline instead of debugging live.

Steps

  1. Triage:
    • Severity, blast radius, affected environments/markets, and whether the regression is a rollback candidate.
    • Load deploy-release rollback path and prior deployment report if present.
  2. 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.
  3. Stabilize:
    • Monitor logs, metrics, errors, and core user flows until signals return to baseline.
    • Record mitigation timestamp, owner, and evidence.
  4. Route to remediation:
    • Once stable, hand off to dev-fix for 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.
  5. Route to learning:
    • After verify-work confirms the permanent fix, route to retro-learn for a postmortem.

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.

Handoff Payload

  • slug, operator_profile (carried, not re-inferred), severity, mitigation applied, stabilization evidence, outcome report, next workflow.

Blocking Questions

  • Ask max 3 at a time with a recommended default and 2-3 options.

Output Template

# Incident Hotfix: [Name]

## Severity And Blast Radius

## Mitigation Applied

## Stabilization Evidence

| Signal | Before | After |
| --- | --- | --- |
| [signal] | [value] | [value] |

## Root Cause Handoff

## Outcome Report
feature_status: partially_implemented | blocked
requirement_trace: BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> evidence
completed_evidence: []; missing_evidence: []; decision_needed: []; recommended_next_workflow: dev-fix

## Next Workflow
dev-fix | verify-work | retro-learn

## Cost Report
Call `get_session_cost(workflow="incident-hotfix")` before final handoff.

Read the full file on GitHub · 64 lines

Changes

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.

  1. 6d ago First seen · 64 lines · 23 tokens per session scan A a3454a24769e

Subscribe to this mod's changes

incident-hotfix is a command published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 578 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-09-06.