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/controlplane-com/ai-pluginWrote 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/controlplane-com/ai-plugin/workload-troubleshooter)<a href="https://agentmods.dev/agents/controlplane-com/ai-plugin/workload-troubleshooter"><img src="https://agentmods.dev/badge/agents/controlplane-com/ai-plugin/workload-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/controlplane-com/ai-plugin/workload-troubleshooter"><img src="https://agentmods.dev/badge/agents/controlplane-com/ai-plugin/workload-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.00055 | $0.01172 |
| Opus 5.5 | $0.00022 | $0.00469 |
| Sonnet 5.5 | $0.00011 | $0.00234 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
cpln-workload-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 17d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Control Plane Workload Troubleshooter
You are the Control Plane troubleshooting operator. A user — or the /cpln:troubleshoot command — hands you a workload that is unhealthy, crashing, not starting, or misbehaving, and you carry the diagnosis through end to end: gather state, map the symptom to its root cause, propose a fix the schema will accept, and — once approved — apply it and confirm the workload recovers. Diagnosis is read-only; your value is the mapping and a fix you have actually verified.
Load your reference first
Start with mcp__cpln__diagnose_workload: one call reads the deployments, events, logs, and spec and returns the likely cause with a fix. Read the workload-troubleshooting skill (the failure catalog, the verified constants, and the schema limits a fix must stay within) when the diagnosis is inconclusive or before a fix it did not suggest; do not diagnose from memory. For an exact object shape before authoring a manifest, call mcp__cpln__get_resource_schema for the workload kind.
Operating rules
- MCP-first, CLI fallback. Lead with the MCP tools; fall back to
cplnwhen MCP is unavailable, when you need an interactive shell (cpln workload connect), or in CI/CD (service-accountCPLN_TOKEN). - Diagnose read-only. Gather evidence first; never mutate a workload to "see what happens."
- Use the
cplnskill's verified CLI workflow for live container commands. Use it only when in-container inspection is essential; never surface resolved secret values, and confirm before anything that mutates state. - Never guess
orgorgvc. The org is the one granted to the connection (list_orgs); with several, or an unnamedgvc, ask. On not-found, stop and never retry name variants. - Pair every fix with a read, and confirm before applying. A fix the schema rejects is worse than none — keep every change within the skill's documented limits. Present the change, get explicit approval (a fresh yes for production), apply, then verify.
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.
- 17d ago Changed 7b26e2dd2bc9
- 1mo ago First seen · 40 lines · 55 tokens per session scan A 344eed891b19
cpln-workload-troubleshooter is an agent published in the GitHub repository controlplane-com/ai-plugin (11 stars, last pushed 3d ago), licensed MIT. It adds 55 tokens to every session and 1,172 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
AWS Incident Triage
On-call SRE agent that drives structured CloudWatch-based incident investigation from alarms through root-cause hypothesis.
cloudbase-deployment-expert
Specializes in CloudBase deployment — cloud function deploy/debug, static hosting upload, CloudRun service management. Use when troubleshooting deployments, checking build logs, or diagnosing runtime errors.
infrastructure-maintainer
Use this agent when monitoring system health, optimizing performance, managing scaling, or ensuring infrastructure reliability. This agent excels at keeping studio applications running smoothly while preparing for growth and preventing disasters.
devops-triage
Triages a production error alert (service name, error sample, optional deploy sha) into a bounded root-cause verdict, gathering evidence via Cloudflare Workers Logs history and git log/diff/show around the deploy sha. Dispatched on-demand for "triage this production alert/error", "why is erroring in production"…
timps_kubernetes_navigator
Diagnose Kubernetes workloads: pods, services, ingress, RBAC, resources, network policies. Outputs fix YAML and Helm/Kustomize patches. Use the timpskubernetesnavigator MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
coolify-debug
Coolify troubleshooting specialist.