DevOps AI Guidelines is a learning and guidance repository for using artificial intelligence in DevOps, including paths toward AI infrastructure architecture and enterprise adoption. It is for DevOps engineers, teams introducing AI, and technical leaders planning AI-enabled operations. The catalogue instruction provides an agent-facing part of these guidelines.
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/VersusControl/devops-ai-guidelinesWrote 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/commands/versuscontrol/devops-ai-guidelines/k8s-troubleshoot)<a href="https://agentmods.dev/commands/versuscontrol/devops-ai-guidelines/k8s-troubleshoot"><img src="https://agentmods.dev/badge/commands/versuscontrol/devops-ai-guidelines/k8s-troubleshoot/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/commands/versuscontrol/devops-ai-guidelines/k8s-troubleshoot"><img src="https://agentmods.dev/badge/commands/versuscontrol/devops-ai-guidelines/k8s-troubleshoot.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.00011 | $0.00209 |
| Opus 5.5 | $0.00004 | $0.00084 |
| Sonnet 5 | $0.00002 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
k8s-troubleshoot 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 11d 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 diagnosing ${input:resource:resource kind and name (e.g. "pod nginx")} in namespace ${input:namespace:namespace}.
Follow this checklist and call MCP tools as needed:
- Run
list_podsfiltered to the namespace and identify pods in non-Ready states. - For each suspect pod, run
describe_resourceand surface:- Container restart counts
Eventsfrom the last 15 minutes- Image pull or scheduling failures
- Pull the last 200 lines of logs via
get_pod_logsfor each affected container. - Produce a root-cause summary with:
- Symptom
- Likely cause
- Recommended next action (do not execute mutations without confirmation)
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.
- 11d ago First seen · 25 lines · 11 tokens per session scan A 1d59dd25c823
k8s-troubleshoot is a command published in the GitHub repository VersusControl/devops-ai-guidelines (1,527 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 209 once invoked, about $0.0000 per session on Opus 5.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-17.
Other commands, from other repositories
debug-pod
Debug a failing or unhealthy Kubernetes pod by analyzing events, logs, and configuration.
debug
Comprehensive debugging for Golden Armada agent services.
doctor
Diagnose the local Spree dev stack — Docker, containers, env, web, migrations, jobs — and prescribe the exact fix.
enforce.docker
Enforce repository-wide compliance with docker.instructions.md.
dev.implement-cli-args-parsing
Evaluate and enforce specific CLI argument parsing discipline across the codebase.
doctor
Cross-plugin system diagnostics — check installed plugins, hook health, build status, and configuration.