security-incident-response SKILL.md skillA
security-incident-response from joaoguirunas/team-os is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add joaoguirunas/team-os/security-incident-response@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- joaoguirunas/team-os
- Path
.claude/skills/security-incident-response/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0, committed Oct 7, 2026
- Size
- 3,978 bytes
- Repository stars
- 5
- License
- MIT
Resposta a incidente de segurança em projetos web — classificação SEV1–SEV4, primeira hora, preservação de evidência, contenção planejada (executada por quem tem autoridade), rotação de credencial sem derrubar o serviço, linha do tempo em UTC e post-mortem com 3–5 correções. Use ao suspeitar ou confirmar vazamento, acesso indevido ou chave exposta.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Resposta a incidente
A squad **prepara e coordena**. Quem executa contenção em produção é o devops da squad de código ou o usuário; quem comunica fora da empresa é o usuário (com advogado, se houver dado pessoal). Esta divisão não é burocracia: contenção errada apaga a evidência e comunicação errada vira passivo.
## 1. Classificação
| SEV | Situação | Exemplo |
|---|---|---|
| **SEV1** | Dado sendo exfiltrado ou alterado agora; acesso indevido ativo | tabela aberta sendo lida em massa; chave usada por terceiro |
| **SEV2** | Exposição confirmada de dado pessoal ou credencial privada, sem uso confirmado | `service_role` no bundle publicado; bucket de contratos aberto |
| **SEV3** | Vulnerabilidade explorável encontrada, sem sinal de exposição | IDOR descoberto em auditoria |
| **SEV4** | Violação de política sem exposição | chave de teste commitada e já revogada |
Na dúvida entre dois níveis, use o mais grave até a evidência dizer o contrário.
## 2. Primeira hora (SEV1/SEV2)
1. **Abrir o registro** em `docs/smart-memory/agents/security/incident/INC-{NN}.md`, horário em **UTC**: o que se sabe, o que não se sabe, quem foi avisado. Marque `[PARCIAL]`.
…Read the whole file at its exact version.
How to install
mdr add joaoguirunas/team-os/security-incident-response@sha256:64ef95684a547851The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_o3tp3db22dlg3bv4)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 7, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3978 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
joaoguirunas/team-os · 5 stars · license MIT · pushed 2026-10-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_o3tp3db22dlg3bv4 GET https://markdownregistry.com/api/v1/resolve?ref=joaoguirunas/team-os/security-incident-response GET https://markdownregistry.com/api/v1/blob/64ef95684a5478510c69d479dedfad7f8ce906455bc91962c906ac73dc4805aa
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.