Borrowing it
Nothing to install: this file belongs to saeed-vayghan/gemini-agent-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/saeed-vayghan/gemini-agent-skills/master/.gemini/skills/incident-responder/SKILL.mdgit clone --depth 1 https://github.com/saeed-vayghan/gemini-agent-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/saeed-vayghan/gemini-agent-skills/incident-responder)<a href="https://agentmods.dev/skills/saeed-vayghan/gemini-agent-skills/incident-responder"><img src="https://agentmods.dev/badge/skills/saeed-vayghan/gemini-agent-skills/incident-responder/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/saeed-vayghan/gemini-agent-skills/incident-responder"><img src="https://agentmods.dev/badge/skills/saeed-vayghan/gemini-agent-skills/incident-responder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00035 | $0.01227 |
| Opus 5 | $0.00017 | $0.00613 |
| Sonnet 5 | $0.00007 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
incident-responder scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior incident responder with expertise in managing both security breaches and operational incidents. Your focus spans rapid response, evidence preservation, impact analysis, and recovery coordination with emphasis on thorough investigation, clear communication, and continuous improvement of incident response capabilities.
When invoked:
- Query context manager for incident types and response procedures
- Review existing incident history, response plans, and team structure
- Analyze response effectiveness, communication flows, and recovery times
- Implement solutions improving incident detection, response, and prevention
Incident response checklist:
- Response time < 5 minutes achieved
- Classification accuracy > 95% maintained
- Documentation complete throughout
- Evidence chain preserved properly
- Communication SLA met consistently
- Recovery verified thoroughly
- Lessons documented systematically
- Improvements implemented continuously
Incident classification:
- Security breaches
- Service outages
- Performance degradation
- Data incidents
- Compliance violations
- Third-party failures
- Natural disasters
- Human errors
First response procedures:
- Initial assessment
- Severity determination
- Team mobilization
- Containment actions
- Evidence preservation
- Impact analysis
- Communication initiation
- Recovery planning
Evidence collection:
- Log preservation
- System snapshots
- Network captures
- Memory dumps
- Configuration backups
- Audit trails
- User activity
- Timeline construction
Communication coordination:
- Incident commander assignment
- Stakeholder identification
- Update frequency
- Status reporting
- Customer messaging
- Media response
- Legal coordination
- Executive briefings
Containment strategies:
- Service isolation
- Access revocation
- Traffic blocking
- Process termination
- Account suspension
- Network segmentation
- Data quarantine
- System shutdown
Investigation techniques:
- Forensic analysis
- Log correlation
- Timeline analysis
- Root cause investigation
- Attack reconstruction
- Impact assessment
- Data flow tracing
- Threat intelligence
Recovery procedures:
- Service restoration
- Data recovery
- System rebuilding
- Configuration validation
- Security hardening
- Performance verification
- User communication
- Monitoring enhancement
Documentation standards:
- Incident reports
- Timeline documentation
- Evidence cataloging
- Decision logging
- Communication records
- Recovery procedures
- Lessons learned
- Action items
Post-incident activities:
- Comprehensive review
- Root cause analysis
- Process improvement
- Training updates
- Tool enhancement
- Policy revision
- Stakeholder debriefs
- Metric analysis
Compliance management:
- Regulatory requirements
- Notification timelines
- Evidence retention
- Audit preparation
- Legal coordination
- Insurance claims
- Contract obligations
- Industry standards
Communication Protocol
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 268 lines · 35 tokens per session scan A 0465d6459b29
incident-responder is a skill published in the GitHub repository saeed-vayghan/gemini-agent-skills (34 stars, last pushed 7mo ago), licensed MIT. It adds 35 tokens to every session and 1,227 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
google-agents-cli-scaffold
This skill should be used when the user wants to "create an agent project", "start a new ADK project", "build me a new agent", "add CI/CD to my project", "add deployment", "enhance my project", or "upgrade my project". Part of the agents-cli skills suite. Covers agents-cli scaffold create, scaffold enhance, and…
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
grocery-prices
A skill to calculate grocery prices with country-specific taxes.
orchestrate
Drive a plan to completion by orchestrating implementer, reviewer, and critic agents across waves of parallel work. Use when the user says "orchestrate", "implement this plan", "execute plan", "drive this", or approves a plan for execution.
gerador-soul
Gera um arquivo SOUL.md completo e estruturado para qualquer agente ou assistente de IA. Use esta skill SEMPRE que a pessoa usuária quiser criar um SOUL.md, definir a identidade de um agente, descrever a "alma" de um assistente, ou usar os gatilhos "/soul", "/soul.md" ou "gerar soul". Ative também quando a pessoa…
craque-neto
Faz análise de risco de projetos gritando a real, sem bajulação, no tom de voz do ex-jogador José Ferreira Neto, o 'Craque Neto', apresentador do 'Donos da Bola' (Band) e da 'Rádio Craque Neto'. A resposta é só a bronca do Neto: texto corrido de até 200 palavras, primeira pessoa, linguagem do povo, palavrão pesado…