Use agent-incident-response

Plan the first hour after something went wrong with an AI coding agent or its tooling

Plan the first hour after something went wrong with an AI coding agent or its tooling — a leaked or stolen API key, a destructive command (a dropped table, a force-push), a runaway bill, a malicious MCP server or skill, an agent prompt-injected into sending data out. It answers the person's actual question first, reads their logs for what they didn't mention, splits a bill from the usage export, gives the exact recovery for what was destroyed, revokes at the provider before cleanup when the evidence says the credential is in someone else's hands, and lays out the first 15 minutes, the next hour and who to tell.

Reach for it when the user says "I leaked my API key", "the agent committed a secret", "the agent deleted / force-pushed / dropped something", "is the table gone for good", "huge bill overnight", "we installed a malicious MCP server", "our agent platform was breached", or "what do I do now".

Install it

npx skilldrop-cli install agent-incident-response                 # Claude Code, your user folder
npx skilldrop-cli install agent-incident-response --project       # Claude Code, this repo
npx skilldrop-cli install agent-incident-response --ide cursor    # or kiro, codex, antigravity, copilot

It is part of the AI engineering pack: --pack ai-engineering installs it with its neighbours.

It ships scripts, so it needs Python 3 (standard library only, nothing to install). What they may touch is declared in its manifest.

Ask for it

Say it the way you would to a colleague. Requests like these route to it:

• "I just realised Claude Code committed my Anthropic API key to the repo an hour ago. What do I do?"
• "our agent ran git push --force on main and a week of commits is gone, help"
• "We installed an MCP server that turns out to be malicious. What do we do now?"
• "Woke up to a $3k OpenAI bill from our agent running overnight, what should I do first"
• "The agent platform we store our API keys in just announced a breach. Next steps?"

Requests like these belong to a different skill, so it shouldn't answer them:

• "Threat-model our support agent before launch: can it be prompt-injected into leaking customer data?"
• "Set a token and spend budget so our agent loop can't run away"
• "Draft the status page update for the API key leak we're dealing with"

If another skill answers instead, ask for this one by name: "use agent-incident-response".

Check what you get

A good result:

• The first line answers the question asked; the second names the kind of incident and its evidence.
• Every figure and time matches the files, sums computed, times in UTC as written.
• What the person didn't mention is found: the second table, caller or repo, the live process.
• Recovery is exact: SHAs, the restore point, the deadline, the caveats, an owner on each action.
• An exposed credential is revoked before cleanup, every one the thing held, with sharing services warned.
• Nothing invented: no environment facts, URLs, figures or attacker actions not in the files.

See a worked example

• injected issue comment

Use something else when

• Designing an agent's controls before anything has gone wrong — agent-threat-model
• Setting token, spend or loop limits ahead of time — agent-budget
• Reviewing an agent's settings, permissions or MCP config when nothing has gone wrong — agent-config-review
• Writing the customer status page or stakeholder update — incident-comms
• The blameless write-up once it's contained — postmortem-generator
• A standing procedure for credential rotation or on-call — runbook-generator

Next

• SKILL.md, the instructions the agent reads
• Its page on the site
• Related: agent-budget, agent-config-review, agent-threat-model, incident-comms, postmortem-generator, runbook-generator

Edit this page on GitHub · View source