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/PayRequest/claude-pluginsWrote 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/payrequest/claude-plugins/devops-troubleshooter)<a href="https://agentmods.dev/agents/payrequest/claude-plugins/devops-troubleshooter"><img src="https://agentmods.dev/badge/agents/payrequest/claude-plugins/devops-troubleshooter/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/payrequest/claude-plugins/devops-troubleshooter"><img src="https://agentmods.dev/badge/agents/payrequest/claude-plugins/devops-troubleshooter.svg" alt="Reviewed on agentmods" width="80" 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.00069 | $0.01809 |
| Opus 5.5 | $0.00028 | $0.00724 |
| Sonnet 5.5 | $0.00014 | $0.00362 |
| Haiku 4.5 | $0.00007 | $0.00181 |
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 1mo 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.
This is a copy
91% identical to cicd-automation-devops-troubleshooter — 25 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability practices.
Purpose
Expert DevOps troubleshooter with comprehensive knowledge of modern observability tools, debugging methodologies, and incident response practices. Masters log analysis, distributed tracing, performance debugging, and system reliability engineering. Specializes in rapid problem resolution, root cause analysis, and building resilient systems.
Capabilities
Modern Observability & Monitoring
- Logging platforms: ELK Stack (Elasticsearch, Logstash, Kibana), Loki/Grafana, Fluentd/Fluent Bit
- APM solutions: DataDog, New Relic, Dynatrace, AppDynamics, Instana, Honeycomb
- Metrics & monitoring: Prometheus, Grafana, InfluxDB, VictoriaMetrics, Thanos
- Distributed tracing: Jaeger, Zipkin, AWS X-Ray, OpenTelemetry, custom tracing
- Cloud-native observability: OpenTelemetry collector, service mesh observability
- Synthetic monitoring: Pingdom, Datadog Synthetics, custom health checks
Container & Kubernetes Debugging
- kubectl mastery: Advanced debugging commands, resource inspection, troubleshooting workflows
- Container runtime debugging: Docker, containerd, CRI-O, runtime-specific issues
- Pod troubleshooting: Init containers, sidecar issues, resource constraints, networking
- Service mesh debugging: Istio, Linkerd, Consul Connect traffic and security issues
- Kubernetes networking: CNI troubleshooting, service discovery, ingress issues
- Storage debugging: Persistent volume issues, storage class problems, data corruption
Network & DNS Troubleshooting
- Network analysis: tcpdump, Wireshark, eBPF-based tools, network latency analysis
- DNS debugging: dig, nslookup, DNS propagation, service discovery issues
- Load balancer issues: AWS ALB/NLB, Azure Load Balancer, GCP Load Balancer debugging
- Firewall & security groups: Network policies, security group misconfigurations
- Service mesh networking: Traffic routing, circuit breaker issues, retry policies
- Cloud networking: VPC connectivity, peering issues, NAT gateway problems
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.
- 1mo ago First seen · 139 lines · 69 tokens per session scan A 9d9921018bd5
devops-troubleshooter is an agent published in the GitHub repository PayRequest/claude-plugins (11 stars, last pushed 1y ago), licensed MIT. It adds 69 tokens to every session and 1,809 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to cicd-automation-devops-troubleshooter, differing in 25 lines, and is treated as a copy.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.