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 commands/controlplane-com/ai-plugin/troubleshootgit clone --depth 1 https://github.com/controlplane-com/ai-pluginWhat 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.00019 | $0.00217 |
| Opus 5 | $0.00010 | $0.00109 |
| Sonnet 5 | $0.00004 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
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 2d 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
Diagnose and fix the Control Plane workload the user named.
Use the cpln-workload-troubleshooter agent — it loads the workload-troubleshooting skill (the full failure catalog) and works read-only first:
- Gather state — per-location deployments and readiness, events, and logs.
- Map the symptom to its root cause: OOMKilled, image pull, secret access, port mismatch, firewall, health probes, resource limits, autoscaling, termination, volumes, service-to-service, or dedicated load balancer.
- Present each issue as what's wrong (with evidence), why, and the exact fix.
- Apply only after I approve, then re-check readiness across locations and confirm the endpoint responds.
If no workload was named, ask for it (and the GVC) — never guess.
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.
- 2d ago First seen · 17 lines · 19 tokens per session scan A 3c18f2f0d2eb
troubleshoot is a command published in the GitHub repository controlplane-com/ai-plugin (10 stars, last pushed 8d ago), licensed MIT. It adds 19 tokens to every session and 217 once invoked, about $0.0001 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 commands, from other repositories
visual-test
Visually test Radar changes against a real cluster using Playwright MCP. Takes screenshots, organizes them, and reports what looks right or wrong.
Issue Spec: Apply
Implement directly or use an optional PROCESS when managed coordination is required.
Issue Spec: Propose
Create or continue proposal, SPEC, QUESTION, design, and TASK artifacts for an issue-spec change.
gen-agent
You are a specialized prompt engineer tasked with generating high-quality, structured prompts for AI agents based on user descriptions. Your goal is to create agent prompts that follow a consistent format inspired by subagent creation workflows, similar to Claude's structured agent design. When you receive an input in…
dependabot-batch
Review Radar's weekly Dependabot updates and batch only soaked, low-risk bumps into one tested PR.
test-radar
Build and test Radar changes using a real running instance. Combines build verification, API smoke tests, and optional Playwright E2E tests.