lean-ir-playbook
Skill2 starsChanged 58 days agoMITView on GitHub
Runs token-efficient incident-response playbook drafting for Cursor and Codex. Produces a compact first-30-minutes checklist for systems the user owns: isolate, preserve, rotate, communicate. Use when the user asks for an IR playbook, incident runbook, first response, or containment steps. Do not use to attack systems, wipe evidence, or bypass access controls.
In this repository21 other files it gives its agents.
- lean-cryptoSkill
- lean-mobileSkill
- lean-privacySkill
- lean-secSkill
- lean-webSkill
- lean-a11ySkill
- lean-depsSkill
- lean-docsSkill
- lean-perfSkill
- lean-reviewSkill
- lean-ciSkill
- lean-cloudSkill
- lean-costSkill
- lean-hardeningSkill
- lean-iotSkill
- lean-netSkill
- lean-dfirSkill
- lean-malwareSkill
- lean-osintSkill
- lean-phishSkill
- lean-threat-modelSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
If evidence files already exist, prefer $lean-dfir for hashing.
- Distinctive: line 46
Do not teach log wiping, anti-forensics, or offensive "to get a dump".
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Lean IR Playbook
Authorized first-response notes. Preserve copies. No offense.
Let SKILL_ROOT be the folder that contains this SKILL.md. Prefer python3; on Windows use py -3.
python3 "$SKILL_ROOT/scripts/lean_ir_playbook.py" template
python3 "$SKILL_ROOT/scripts/lean_ir_playbook.py" check /path/to/playbook.jsonIf evidence files already exist, prefer $lean-dfir for hashing. This skill writes the human checklist.
Mode
Default lean.
| Mode | Budget |
lean | 1 incident type; references/first30.md; ≤8 steps |
standard | + comms; ≤12 steps |
deep | still no wipe/exploit; ≤16 steps |
Workflow
- Name the incident class (stolen laptop, ransomware note they already have, leaked key, phishing click).
- Fill isolate → preserve → rotate → communicate → recover.
checkJSON. Do not invent legal advice.
Hard rules
- Systems the user administers only.
- Do not teach log wiping, anti-forensics, or offensive "to get a dump".
- Credentials:
[REDACTED]; rotate at the provider.
Report template
## Lean-ir-playbook (`<mode>`)
**Incident class:** <name>
| When | Action | Owner | Done when |
|------|--------|-------|-----------|
| 0-15m | isolate host they own | on-call | NIC down / token revoked |Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.