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 agentmods add commands/danielbodnar/skills/incidentgit clone --depth 1 https://github.com/danielbodnar/skillsWhat 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 | $0.00000 | $0.00455 |
| Opus 5 | $0.00000 | $0.00228 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
incident 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 2d 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.
What it actually says
Generate Incident Report
Create a comprehensive incident report for current or recent issues:
-
Incident Detection:
- Query list_raised_alerts for active issues
- Check find_anomalous_metrics for unusual behavior
- Review alert_transitions for recent state changes
- Identify incident start time
-
Impact Assessment:
- Severity level (P1/P2/P3)
- Affected services/containers
- Performance degradation metrics
- User impact estimation
-
Timeline Construction:
- Query alert_transitions for event sequence
- Get metric data around incident time
- Identify initial trigger event
- Document propagation of issues
- Note when issues were detected
-
Root Cause Analysis:
- Use find_correlated_metrics for incident period
- Analyze metrics that changed significantly
- Identify primary vs secondary causes
- Check for cascading failures
-
Supporting Data:
- Container resource usage during incident
- System metrics (CPU, memory, I/O, network)
- Process list at time of incident
- Log excerpts if relevant
-
Remediation Actions Taken:
- Document what was done to resolve
- Include timestamps of actions
- Note effectiveness of each action
-
Lessons Learned:
- What worked well
- What could be improved
- Monitoring gaps identified
- Process improvements needed
-
Follow-up Actions:
- Short-term fixes needed
- Long-term improvements
- Monitoring enhancements
- Documentation updates
For the current known incident (2025-10-21):
- Swap exhaustion (99.99%)
- MySQL memory spike (6.6 GB → 12.9 GB at 19:51 UTC)
- Disk space warning (94% full)
Generate report in markdown format suitable for:
- Saving to reports/ directory
- Sharing with team
- Post-mortem analysis
- Incident tracking system
Include:
- Executive summary
- Detailed timeline
- Technical analysis
- Graphs/charts (text-based if needed)
- Action items with owners
- Prevention recommendations
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.
- 2d ago First seen · 71 lines · 0 tokens per session scan A 87756797f22f
incident is a command published in the GitHub repository danielbodnar/skills (2 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 455 tokens. 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.