Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ricneves-ai/flowgrammers-skills --skill incident-commandergit clone --depth 1 https://github.com/ricneves-ai/flowgrammers-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/ricneves-ai/flowgrammers-skills/incident-commander)<a href="https://agentmods.dev/skills/ricneves-ai/flowgrammers-skills/incident-commander"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/incident-commander/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/ricneves-ai/flowgrammers-skills/incident-commander"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/incident-commander.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.00053 | $0.04225 |
| Opus 5 | $0.00026 | $0.02112 |
| Sonnet 5 | $0.00011 | $0.00845 |
| Haiku 4.5 | $0.00005 | $0.00422 |
Grade A, and why
incident-commander 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 9d 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 — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Incident Commander
Categoria: Engineering Team
Tier: POWERFUL
Versão: 1.0.0
Última Atualização: Fevereiro de 2026
Visão Geral
A skill Incident Commander fornece um framework abrangente de resposta a incidentes para gerenciar incidentes tecnológicos desde a detecção até a resolução e revisão pós-incidente. Esta skill implementa práticas testadas em batalha de equipes SRE e DevOps em escala, fornecendo ferramentas estruturadas para classificação de severidade, reconstrução de linha do tempo e análise pós-incidente completa.
Funcionalidades Principais
- Classificação Automatizada de Severidade - Triagem inteligente de incidentes com base em métricas de impacto e urgência
- Reconstrução de Linha do Tempo - Transformar logs e eventos dispersos em narrativas coerentes de incidentes
- Geração de Revisão Pós-Incidente - PIRs estruturados com múltiplos frameworks de RCA
- Templates de Comunicação - Templates pré-construídos para atualizações de partes interessadas e escalações
- Integração de Runbook - Gerar runbooks acionáveis a partir de padrões de incidentes
Skills Incluídas
Ferramentas Principais
-
Classificador de Incidentes (
incident_classifier.py)- Analisa descrições de incidentes e produz níveis de severidade
- Recomenda equipes de resposta e ações iniciais
- Gera templates de comunicação com base na severidade
-
Reconstrutor de Linha do Tempo (
timeline_reconstructor.py)- Processa eventos com timestamp de múltiplas fontes
- Reconstrói a linha do tempo cronológica do incidente
- Identifica lacunas e fornece análise de duração
-
Gerador de PIR (
pir_generator.py)- Cria documentos abrangentes de Revisão Pós-Incidente
- Aplica múltiplos frameworks de RCA (5 Porquês, Espinha de Peixe, Linha do Tempo)
- Gera itens de acompanhamento acionáveis
Framework de Resposta a Incidentes
Sistema de Classificação de Severidade
SEV1 - Interrupção Crítica
Definição: Falha completa de serviço afetando todos os usuários ou funções críticas de negócios
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.
- 9d ago First seen · 478 lines · 53 tokens per session scan A a09d4639693e
incident-commander is a skill published in the GitHub repository ricneves-ai/flowgrammers-skills (112 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 4,225 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…