security-incident-response
Skill0 starsChanged 27 days agoMITView on GitHub
Coordinate containment, eradication, and recovery for an authorized incident. Preserve evidence, communicate facts, and avoid destructive actions without approval.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Kin9Zeus/senior-engineer-skillstheir own version, first seen Nov 1, 2026
- mawero83/google-sre-skillstheir own version, first seen Nov 1, 2026
- joaoguirunas/team-ostheir own version, first seen Oct 13, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- mawero83/google-sre-skills★ 18same name
- joaoguirunas/team-os★ 6same name
- Kin9Zeus/senior-engineer-skills★ 3same 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 repository219 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/behavioral-discipline.mdcCursor rule
- .cursor/rules/context-budget.mdcCursor rule
- .cursor/rules/orchestration.mdcCursor rule
- .cursor/rules/yagni-stdlib.mdcCursor rule
- androidSkill
- android-ui-designSkill
- api-versioningSkill
- astroSkill
- auth-token-inspectorSkill
- backlogSkill
- cc-api-contractSkill
- cc-db-migrationSkill
- cc-featureSkill
- cc-fixSkill
- cc-pagespeedSkill
- cc-refactorSkill
- cc-reviewSkill
- cc-spec-mutationSkill
- cc-tdd-cycleSkill
- cc-test-planSkill
- code-reviewSkill
- commitSkill
- conductor-setupSkill
- councilSkill
- database-migrationsSkill
- django-ormSkill
- django-testingSkill
- django-uvSkill
- drizzle-schema-architectSkill
- evaluationSkill
- fastapi-pydantic-strictSkill
- find-skillsSkill
- jpa-nplusone-detectorSkill
- jpa-postgresSkill
- laravel-specialistSkill
- livewire-alpine-bridgeSkill
- multi-agent-orchestrationSkill
- nextjs-typescriptSkill
- openspecSkill
- pagespeed-insightsSkill
- pagespeed-perfSkill
- php-proSkill
- python-django-stackSkill
- python-fastapi-stackSkill
- pythonSkill
- rust-asyncSkill
- rust-engineeringSkill
- rust-sqlxSkill
- security-ai-llmSkill
- security-blue-teamSkill
- security-cloudSkill
- security-cryptoSkill
- security-exploit-devSkill
- security-grcSkill
- security-log-analysisSkill
- security-malware-analysisSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use this skill only with explicit written authorization for a named scope (systems, environments, and time window).
- Distinctive: line 20
Follow the org IR plan: detect, contain, eradicate, recover, lessons
- Distinctive: line 31
Do not produce exploit payloads, malware, or attack procedures.
≈ “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
Incident Response
Authorization
Use this skill only with explicit written authorization for a named scope (systems, environments, and time window). If authorization is missing, expired, or the request is for someone else's systems, stop.
This skill is defensive and owner-authorized. It does not authorize offensive cyber operations.
Do
- Follow the org IR plan: detect, contain, eradicate, recover, lessons
- Preserve logs and disk images before reboot or wipe
- Redact secrets from tickets and chat
- Track timeline, systems, and decision-makers
Do not
- Wipe systems before evidence capture unless imminent ransomware spread is approved
- Blame individuals in the working notes; stick to systems and facts
- Reuse attacker tooling from the incident as a 'test'
- Do not produce exploit payloads, malware, or attack procedures.
How to Use
Load this skill from /cc-security when the Task Card domain is security-incident-response.
Example prompts:
P1: suspected token theft on api-prod. Draft containment and evidence steps for the IR commander.After containment, write the lessons-learned outline and the regression tests we should add.
Integration
- Workflow:
/cc-security(CCEP commandsecurity) - Existing OWASP application-security skill remains
security(not this id) - High-risk changes still require
security-reviewer
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.