devops-troubleshooter

devops-troubleshooter is an agent for coding agents from rafaelkamimura/claude-tools. It costs 42 tokens per session (227 once invoked), scanned A, a copy of devops-troubleshooter, MIT.

A specialist for diagnosing production software problems using logs, measurements, and deployment information. Production means the live system used by customers.

In plain words
What is it for?
Investigating incidents, debugging containers and networks, rolling back deployments, applying temporary or permanent fixes, and documenting prevention steps.
Why use it?
It gives a structured way to find the cause of outages, failed deployments, slowdowns, memory problems, and network issues.

Agent

Part of the claude-tools plugin — 12 commands, 46 agents shipped together

Install

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.

agentmods
npx agentmods add agents/rafaelkamimura/claude-tools/devops-troubleshooter
Clone the repo
git clone --depth 1 https://github.com/rafaelkamimura/claude-tools

Or install claude-tools, the plugin that ships this one along with the rest of its 12 commands, 46 agents.

Wrote 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.

agentmods badge for devops-troubleshooter

README.md
[![agentmods](https://agentmods.dev/badge/agents/rafaelkamimura/claude-tools/devops-troubleshooter.svg)](https://agentmods.dev/agents/rafaelkamimura/claude-tools/devops-troubleshooter)
Your own site
<a href="https://agentmods.dev/agents/rafaelkamimura/claude-tools/devops-troubleshooter"><img src="https://agentmods.dev/badge/agents/rafaelkamimura/claude-tools/devops-troubleshooter.svg" alt="Measured on agentmods" height="20"></a>
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 227 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 92% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00042 $0.00227
Opus 5 $0.00021 $0.00113
Sonnet 5 $0.00008 $0.00045
Haiku 4.5 $0.00004 $0.00023

Measured 5d ago against content hash 2dfaf0af7d87, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 5d 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.

Origin

This is a copy

92% identical to devops-troubleshooter — 2 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.

agents/devops-troubleshooter.md · 33 lines

What it actually says

You are a DevOps troubleshooter specializing in rapid incident response and debugging.

Focus Areas

  • Log analysis and correlation (ELK, Datadog)
  • Container debugging and kubectl commands
  • Network troubleshooting and DNS issues
  • Memory leaks and performance bottlenecks
  • Deployment rollbacks and hotfixes
  • Monitoring and alerting setup

Approach

  1. Gather facts first - logs, metrics, traces
  2. Form hypothesis and test systematically
  3. Document findings for postmortem
  4. Implement fix with minimal disruption
  5. Add monitoring to prevent recurrence

Output

  • Root cause analysis with evidence
  • Step-by-step debugging commands
  • Emergency fix implementation
  • Monitoring queries to detect issue
  • Runbook for future incidents
  • Post-incident action items

Focus on quick resolution. Include both temporary and permanent fixes.

Changes

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.

  1. 5d ago First seen · 33 lines · 42 tokens per session scan A 2dfaf0af7d87

Subscribe to this mod's changes

devops-troubleshooter is an agent published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 8mo ago), licensed MIT. It adds 42 tokens to every session and 227 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to devops-troubleshooter, differing in 2 lines, and is treated as a copy.