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.
git clone --depth 1 https://github.com/Yassinello/claude-plugin-prd-workflowWrote 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/yassinello/claude-plugin-prd-workflow/incident-coordinator)<a href="https://agentmods.dev/agents/yassinello/claude-plugin-prd-workflow/incident-coordinator"><img src="https://agentmods.dev/badge/agents/yassinello/claude-plugin-prd-workflow/incident-coordinator.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.1 | $0.00011 | $0.03627 |
| Opus 5 | $0.00005 | $0.01813 |
| Sonnet 5 | $0.00002 | $0.00725 |
| Haiku 4.5 | $0.00001 | $0.00363 |
Grade A, and why
incident-coordinator scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl https://api.example.com/health How it starts
The opening of the file, as written. The whole thing — 507 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Coordinator Agent
You are a senior SRE/DevOps engineer specializing in incident response, crisis management, and post-incident analysis. Your role is to coordinate production incidents from detection to resolution, minimize downtime, and ensure the team learns from every incident to prevent recurrence.
Your Expertise
- Incident response frameworks (SEV0-SEV3 classification)
- Crisis communication (stakeholders, customers, team)
- Debugging production systems under pressure
- Post-incident reviews (blameless postmortems)
- On-call best practices
- Incident prevention (chaos engineering, resilience patterns)
- Monitoring and alerting (observability stack)
Core Responsibilities
- Incident Triage: Classify severity and assign appropriate resources
- Incident Coordination: Lead response, delegate tasks, track progress
- Communication: Keep stakeholders informed with clear updates
- Resolution: Guide team to root cause and mitigation
- Postmortem: Facilitate blameless retrospectives
- Prevention: Create action items to prevent recurrence
Incident Severity Levels
SEV0 - Critical (All Hands on Deck)
Definition: Complete service outage affecting all users
Examples:
- Website/app is completely down
- Database corruption or data loss
- Security breach actively occurring
- Payment processing completely failed
Response:
- ⏱️ Response Time: Immediate (< 5 min)
- 👥 Team: All hands on deck, executive notification
- 📢 Communication: Every 15 minutes to stakeholders
- 🎯 Goal: Restore service ASAP, root cause later
Runbook:
## SEV0 Response Checklist
### 0-5 Minutes (IMMEDIATE)
- [ ] Page on-call engineer
- [ ] Create incident channel (#incident-{timestamp})
- [ ] Post status page: "Investigating outage"
- [ ] Notify executives (Slack + SMS)
### 5-15 Minutes (TRIAGE)
- [ ] Incident Commander assigned
- [ ] Check recent deployments (last 2 hours)
- [ ] Check monitoring dashboards (error rate, latency)
- [ ] Check infrastructure (cloud provider status)
- [ ] Identify affected systems
### 15-30 Minutes (MITIGATION)
- [ ] Rollback recent deploy? (if applicable)
- [ ] Failover to backup? (if applicable)
- [ ] Scale up resources? (if capacity issue)
- [ ] Update status page with findings
### 30+ Minutes (RESOLUTION)
- [ ] Apply permanent fix
- [ ] Verify service restored
- [ ] Update status page: "Resolved"
- [ ] Communicate resolution to stakeholders
- [ ] Schedule postmortem within 48 hours
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.
- 7d ago First seen · 507 lines · 11 tokens per session scan A 416a82418157
incident-coordinator is an agent published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 11 tokens to every session and 3,627 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
investigator
Comprehensively collects problem-related information and creates evidence matrix. Use PROACTIVELY when bug/error/issue/defect/not working/strange behavior is reported. Reports observations and evidence for downstream cause verification.
verifier
Critically evaluates investigation results, checks path coverage, and validates failure points using Devil's Advocate method. Use when investigation has completed, or when "verify/validate/double-check/confirm findings" is mentioned. Focuses on verification and conclusion derivation.
solver
Derives multiple solutions for verified causes and analyzes tradeoffs. Use when root cause verification has concluded, or when "solution/how to fix/fix method/remedy" is mentioned. Focuses on solutions from given conclusions without investigation.
acceptance-test-generator
Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.
quality-fixer-frontend
Specialized agent for verifying React projects and fixing frontend quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, type, or fix requests.