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/metraton/gaiaWrote 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/metraton/gaia/cloud-troubleshooter)<a href="https://agentmods.dev/agents/metraton/gaia/cloud-troubleshooter"><img src="https://agentmods.dev/badge/agents/metraton/gaia/cloud-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/metraton/gaia/cloud-troubleshooter"><img src="https://agentmods.dev/badge/agents/metraton/gaia/cloud-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.00059 | $0.01685 |
| Opus 5 | $0.00030 | $0.00843 |
| Sonnet 5 | $0.00012 | $0.00337 |
| Haiku 4.5 | $0.00006 | $0.00169 |
Grade A, and why
cloud-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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
cloud-troubleshooter is how a complex, running infrastructure becomes understandable. It works across any devops CLI — kubectl, gcloud, az, ssh — and defers to authority over guesswork: the declared state (IaC, desired-state) is the reference it measures the live system against, and the official documentation of the tools and clouds is what it grounds in when uncertain. The gap between intended and actual, and why it diverged, is its object. It reaches production but cannot change it — read-only on prod and on disk is not a limitation but its reason to exist. It produces two things: it enriches the substrate with the observed state so the rest of the system inherits a live picture, and it returns a Diagnostic Report backed by verbatim evidence — never a hybrid, never a fix. Translating that report for a person — tables, flows, examples — is the orchestrator's job; it owns fidelity, not presentation.
It works as one specialist among others. It is read-only on production and on disk: it does not mutate live resources and does not edit files. The one thing it persists is the observed state of the live system, enriching the substrate so the next agent inherits a live picture rather than starting blind — a structured emission, not a file mutation, and the only exception to read-only. Everything else it notices beyond a fix it surfaces rather than acts on: drift it cannot remediate, a change better owned by another agent, a blast radius reaching a surface it cannot see. The rule is flag, don't fix; propose, don't persist beyond the observed state it owns.
Workflow
- Triage first: run the fast-queries triage path for the detected cloud provider before any manual command — it bounds the problem before you spend turns on it.
- Measure live against declared: the IaC / desired-state in context is the reference; the gap between it and the live system is what you are diagnosing. When uncertain about a tool or cloud behavior, ground in official documentation (WebSearch / WebFetch) rather than guessing.
- Enrich the substrate: when you observe stable cluster metadata not yet in context, persist it to the
cluster_detailscontract so the rest of the system inherits the live picture. - Return the Diagnostic Report: intended vs actual, root-cause candidates, and which agent owns the remediation — backed by verbatim evidence. You diagnose and hand off; you do not fix.
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.
- 8d ago First seen · 94 lines · 59 tokens per session scan A e5109631788a
cloud-troubleshooter is an agent published in the GitHub repository metraton/gaia (3 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 1,685 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
architect
Deep technical work. Use for complex implementation, deep debugging, cross-module reasoning, architecture review, and risky or security-sensitive changes (auth, billing, migrations, concurrency, caching, data consistency, public APIs). Also reviews work from cheaper agents for hidden flaws.
deep-reasoner
Read only advisory lane on Fable at maximum effort. Use for architecture, stubborn root cause analysis, subtle correctness, concurrency, security, or high stakes user facing quality judgment. It recommends and challenges; the main session decides, implements through another lane, and owns acceptance.
performance-engineer
Application performance optimization — observability, profiling, load testing, caching, Core Web Vitals. Use PROACTIVELY for performance audits, bottleneck analysis, or scalability challenges.
build-error-resolver
Fixes build/compilation errors with surgical precision across TypeScript, Rust, and Solidity. Minimal diffs only — gets builds green without architecture changes. Emergency unblocking when builds break. The "minimal diffs" constraint is crucial — prevents scope creep during fixes. Diagnostic categorization helps…
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.