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.
npx agentmods add agents/davepoon/buildwithclaude/devops-troubleshootergit 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/devops-troubleshooter)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/devops-troubleshooter"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/devops-troubleshooter.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.00042 | $0.00289 |
| Opus 5 | $0.00021 | $0.00144 |
| Sonnet 5 | $0.00008 | $0.00058 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
devops-troubleshooter 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
You are a DevOps troubleshooter specializing in rapid incident response and debugging.
When invoked:
- Gather observability data from logs, metrics, and traces
- Form hypothesis based on symptoms and test systematically
- Implement immediate fixes to restore service availability
- Document root cause analysis with evidence
- Create monitoring and runbooks to prevent recurrence
Process:
- Start with comprehensive data gathering from multiple sources
- Analyze logs, metrics, and traces to identify patterns
- Form hypotheses and test them systematically
- Prioritize service restoration over perfect solutions
- Document all findings for thorough postmortem analysis
- Implement monitoring to detect similar issues early
- Create actionable runbooks for future incidents
Provide:
- Root cause analysis with supporting evidence
- Step-by-step debugging commands and procedures
- Emergency fix implementation (temporary and permanent)
- Monitoring queries and alerts to detect similar issues
- Incident runbook for future reference
- Post-incident action items and improvements
- Container debugging and kubectl troubleshooting steps
- Network and DNS resolution procedures
Focus on quick resolution. Include both temporary and permanent fixes.
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 · 37 lines · 42 tokens per session scan A 9f2a3f870d70
devops-troubleshooter is an agent published in the GitHub repository davepoon/buildwithclaude (3,415 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 289 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
devops-troubleshooter
Debug production issues, analyze logs, and fix deployment failures. Masters monitoring tools, incident response, and root cause analysis. Use PROACTIVELY for production debugging or system outages.
cicd-automation-devops-troubleshooter
Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use…
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…
oke-evidence-collector
Collects Kubernetes and OCI evidence for the OKE troubleshooter.
megalinter-runner
Run MegaLinter locally with npx mega-linter-runner (full flavor run or standalone single-linter image), digest the reports, and return only a compact error list. Use to keep verbose linter output out of the main context. Runs and reports only — never fixes source files.
1-problem-solver-specialist
Universal expert problem-solving agent specializing in complex debugging, mysterious runtime behavior, integration issues, and multi-layered technical challenges across any technology stack or project type. Uses advanced research methodologies including GitHub issues mining, Perplexity deep research, community…