davepoon/buildwithclaude is a discovery hub and plugin marketplace for Claude Code extensions, including agents, commands, hooks, skills, plugins, MCP servers, and marketplace collections. Developers use it to browse, search, and find installation instructions for tools that extend Claude-related workflows. Catalogue entries include agents, plugins, commands, and skills from this collection.
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/davepoon/buildwithclaudeWrote 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/davepoon/buildwithclaude/incident-responder)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/incident-responder"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/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.1 | $0.00036 | $0.00241 |
| Opus 5 | $0.00018 | $0.00120 |
| Sonnet 5 | $0.00007 | $0.00048 |
| Haiku 4.5 | $0.00004 | $0.00024 |
Grade A, and why
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.
What it actually says
You are an incident response specialist acting with urgency while maintaining precision when production is down or degraded.
When invoked:
- Assess severity - user impact, business impact, system scope
- Stabilize immediately - identify quick mitigation options
- Gather data - recent deployments, error logs, metrics
- Implement minimal viable fix with monitoring
- Document timeline and prepare post-mortem
Process:
- Start with error aggregation and pattern identification
- Check for recent deployments or configuration changes
- Consider rollback, resource scaling, or feature disabling
- Implement circuit breakers for cascading failures
- Communicate status every 15 minutes to stakeholders
Provide:
- Immediate severity assessment and impact analysis
- Quick mitigation options and temporary fixes
- Root cause analysis with supporting evidence
- Fix implementation plan with rollback strategy
- Post-incident report with timeline and lessons learned
- Prevention recommendations for similar incidents
Act with urgency while maintaining precision - production stability is critical.
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 · 31 lines · 36 tokens per session scan A 0a7c47b985b8
incident-responder is an agent published in the GitHub repository davepoon/buildwithclaude (3,421 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 241 once invoked, about $0.0002 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 agents, from other repositories
code-searcher
Use for codebase analysis, forensic examination, and code mapping — locating functions, classes, and logic; security vulnerability analysis; pattern detection; architectural consistency checks; and navigable code references with exact file:line numbers. Delegate when the user needs to find where code lives, understand…
d1-debugger
Autonomous diagnostic agent that investigates Cloudflare D1 database issues through 9-phase analysis (config, migrations, queries, bindings, errors, limits, performance, Time Travel, report). Use when encountering D1 query errors, migration failures, binding issues, performance degradation, or limit/quota errors.
do-debugger
Autonomous Durable Objects debugger. Automatically detects and fixes DO configuration errors, runtime issues, and common mistakes without user intervention.
queue-debugger
Use this agent when the user encounters "queue not delivering messages", "consumer errors", "DLQ filling up", "throughput issues", "message backlog", "queue timeout errors", or needs systematic Cloudflare Queues troubleshooting. Examples.
troubleshooting-agent
This agent should be used when the user asks to "debug Cloudflare Images errors", "troubleshoot upload failures", "diagnose CORS issues", "fix transformation errors", or encounters errors 5408, 9401-9413, multipart/form-data encoding issues, or API connectivity problems.
Turnstile CSP Debugger
This agent should be used when the user asks to "validate CSP for turnstile", "fix CSP errors", "check content security policy", or encounters error 200500. Analyzes Content Security Policy headers and suggests Turnstile-compatible configurations.