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/hermeticormus/claude-code-game-development/devops-troubleshootergit clone --depth 1 https://github.com/HermeticOrmus/claude-code-game-developmentWrote 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/hermeticormus/claude-code-game-development/devops-troubleshooter)<a href="https://agentmods.dev/agents/hermeticormus/claude-code-game-development/devops-troubleshooter"><img src="https://agentmods.dev/badge/agents/hermeticormus/claude-code-game-development/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 | $0.00069 | $0.01809 |
| Opus 5 | $0.00034 | $0.00905 |
| Sonnet 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 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.
This is a copy
100% identical to devops-troubleshooter — 0 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.
- 4d ago First seen · 139 lines · 69 tokens per session scan A 7451695cbc36
devops-troubleshooter is an agent published in the GitHub repository HermeticOrmus/claude-code-game-development (59 stars, last pushed 3mo ago), licensed MIT. It adds 69 tokens to every session and 1,809 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to devops-troubleshooter, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
prototyper
Rapid prototyping specialist for pre-production. Builds quick, throwaway implementations to validate game concepts and mechanics. Use during pre-production for concept validation, vertical slices, or mechanical experiments. Standards are intentionally relaxed for speed.
lattice-architect
The visionary. Designs the public API of a Lattice package before a line of it is implemented, and says what the kit is missing. Use before any builder starts, and whenever two packages disagree about a shape.
gamemaker-assets-specialist
The GameMaker Assets Specialist owns all GMS2 asset pipeline management: texture groups, texture pages, audio groups, sprite packing strategy, asset import settings, VRAM budgets, and content loading optimization. They ensure fast load times and controlled memory usage across all target platforms.
economy-designer
The Economy Designer specializes in resource economies, loot systems, progression curves, and in-game market design. Use this agent for loot table design, resource sink/faucet analysis, progression curve calibration, or economic balance verification.
游戏设计师
你是一位资深游戏系统与机制设计师。你将创意愿景转化为文档化、可实现的设计方案。你的思维围绕循环、调节杠杆和玩家动机展开。.
godot-csharp-specialist
The Godot C# specialist owns all C# code quality in Godot 4 projects: .NET patterns, attribute-based exports, signal delegates, async patterns, type-safe node access, and C#-specific Godot idioms. They ensure clean, performant, type-safe C# that follows .NET and Godot 4 idioms correctly.