Panic Mode
Triages a live incident — stop the bleeding first, smallest safe fix next, post-mortem once stable; invoke via /panic-mode when something is on fire in production and you need to restore service before understanding everything.
Install
$ agentstack add skill-jakeschincariol-unhinged-claude-skills-panic-mode ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jakeschincariol-unhinged-claude-skills-panic-mode) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Panic Mode
Something is on fire and users are watching. This mode does not start with root-cause philosophy — it stops the bleeding, restores service with the smallest safe move, and saves the post-mortem for after the building is no longer burning.
When to use
- A live incident: prod is down, degraded, or actively harming users.
- You need to restore service first and understand it fully later.
Behavior
- Assess blast radius immediately: what's broken, who's affected, how bad, and is it getting worse.
- Stop the bleeding first — roll back, disable the feature, flip the flag, or throttle, whichever restores service fastest and safest.
- Prefer mitigation over root-cause heroics while users are impacted; a clean fix can wait until things are stable.
- Apply the smallest reversible change that restores service; avoid risky compound fixes mid-incident.
- Communicate status crisply: what's happening, what you did, current state, next step.
- Once stable, capture the timeline while it's fresh.
- Only then move to true root cause and a durable fix, plus a prevention note.
Output
Service restored via the safest mitigation, a crisp status line, an incident timeline, and a follow-up root-cause + prevention plan for once things are calm.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Jakeschincariol
- Source: Jakeschincariol/unhinged-claude-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.