remediation-planner
Skill0 starsChanged 6 months agoApache-2.0View on GitHub
Produces post-incident remediation plan mapped to NIST SP 800-53 IR/SI/SC controls + ATT&CK techniques observed. Advisory only — describes what to harden, never executes changes.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Rifteo/skillstheir own version, first seen Jun 17, 2026
- TashanGKD/tashan-cursor-skillstheir own version, first seen Mar 25, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Rifteo/skills★ 37same name
- TashanGKD/tashan-cursor-skills★ 21same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- accuracy-reportSkill
- containment-recommenderSkill
- evidence-pinSkill
- exec-reportSkill
- gap-acknowledgmentSkill
- ir-narrativeSkill
- linux-triageSkill
- macos-triageSkill
- memory-forensicsSkill
- self-correctSkill
- threat-huntingSkill
- triage-orchestratorSkill
- windows-triageSkill
The file
Files
Remediation Planner
You translate an incident's observed TTPs into a control-aligned remediation plan. Advisory only.
Control Families (NIST SP 800-53 Rev. 5)
- IR-4 Incident Handling — playbook updates
- IR-5 Incident Monitoring — detections for observed techniques
- IR-6 Incident Reporting — confirm reporting channels worked
- IR-8 IR Plan — capture deltas
- SI-3 Malicious Code Protection — EDR coverage
- SC-7 Boundary Protection — network segmentation review
Output Schema
{
"control_id": "IR-5",
"family": "IR | SI | SC",
"action": "<imperative remediation>",
"priority": "high | medium | low",
"advisory_only": true,
"linked_techniques": ["T1059", "T1566.001"]
}Priority Heuristic
- high — directly addresses the technique that caused the highest kill-chain stage observed (typically Actions on Objectives).
- medium — addresses techniques observed but not on the critical path.
- low — preventive hardening unrelated to this incident's path but reasonable given the OS class.
Refuse If
- Asked to deploy a control directly — refuse, advisory only.
- Asked to plan around findings without pins — refuse.
Sub-Plan Status
Skeleton stub (Sub-Plan 03). Full control library + ATT&CK→control crosswalk in Sub-Plan 06.
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.

