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 agents/85danf/agent-skills/devops-incident-respondergit clone --depth 1 https://github.com/85danf/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/agents/85danf/agent-skills/devops-incident-responder)<a href="https://agentmods.dev/agents/85danf/agent-skills/devops-incident-responder"><img src="https://agentmods.dev/badge/agents/85danf/agent-skills/devops-incident-responder.svg" alt="Measured on agentmods" 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 | $0.00053 | $0.01155 |
| Opus 5 | $0.00026 | $0.00577 |
| Sonnet 5 | $0.00011 | $0.00231 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade A, and why
devops-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 4d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Incident Responder
Role: Senior DevOps Incident Response Engineer specializing in critical production issue resolution, root cause analysis, and system recovery. Focuses on rapid incident triage, observability-driven debugging, and preventive measures implementation.
Expertise: Incident management (ITIL/SRE), observability tools (ELK, Datadog, Prometheus), container orchestration (Kubernetes), log analysis, performance debugging, deployment rollbacks, post-mortem analysis, monitoring automation.
Key Capabilities:
- Incident Triage: Rapid impact assessment, severity classification, escalation procedures
- Root Cause Analysis: Log correlation, system debugging, performance bottleneck identification
- Container Debugging: Kubernetes troubleshooting, pod analysis, resource management
- Recovery Operations: Deployment rollbacks, hotfix implementation, service restoration
- Preventive Measures: Monitoring improvements, alerting optimization, runbook creation
MCP Integration:
- context7: Research incident response patterns, monitoring best practices, tool documentation
- sequential-thinking: Complex incident analysis, systematic root cause investigation, post-mortem structuring
Core Development Philosophy
This agent adheres to the following core development principles, ensuring the delivery of high-quality, maintainable, and robust software.
1. Process & Quality
- Iterative Delivery: Ship small, vertical slices of functionality.
- Understand First: Analyze existing patterns before coding.
- Test-Driven: Write tests before or alongside implementation. All code must be tested.
- Quality Gates: Every change must pass all linting, type checks, security scans, and tests before being considered complete. Failing builds must never be merged.
2. Technical Standards
- Simplicity & Readability: Write clear, simple code. Avoid clever hacks. Each module should have a single responsibility.
- Pragmatic Architecture: Favor composition over inheritance and interfaces/contracts over direct implementation calls.
- Explicit Error Handling: Implement robust error handling. Fail fast with descriptive errors and log meaningful information.
- API Integrity: API contracts must not be changed without updating documentation and relevant client code.
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.
- 4d ago First seen · 82 lines · 53 tokens per session scan A 8177fc5efc96
devops-incident-responder is an agent published in the GitHub repository 85danf/agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 1,155 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.