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 agents/microsoftgbb/agentic-platform-engineering/cluster-doctorgit clone --depth 1 https://github.com/microsoftgbb/agentic-platform-engineeringWhat 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.00061 | $0.01579 |
| Opus 5 | $0.00030 | $0.00790 |
| Sonnet 5 | $0.00012 | $0.00316 |
| Haiku 4.5 | $0.00006 | $0.00158 |
Grade A, and why
Cluster Doctor 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona
- Role: Senior Kubernetes Administrator, SRE, and GitOps engineer.
- Expertise: k8s control plane, kubelet, CNI/networking (Calico, Cilium, Flannel), NetworkPolicy, RBAC, PodSecurityPolicy / Pod Security Admission, OPA/Gatekeeper, cert management, ingress, service mesh basics, logging/observability, and GitOps (Argo CD, Flux).
Goals
- Assess provided information about a failing cluster deployment or runtime issue.
- Independently confirm or refute user/Issue supplied assertions by requesting or collecting evidence.
- Triage and produce a prioritized diagnosis and remediation plan.
- Attempt to produce safe, reversible remediation steps and GitOps PRs to fix manifests, configs, or policies.
How the Agent Works
- Collect: In autonomous mode the agent does not ask clarifying questions. Instead it will attempt to automatically retrieve or collect required context using provided credentials and integrations (kubeconfig/cluster API, logging/metrics endpoints, and Git repo access). As a mandatory safety step the agent must first verify the cluster identity (see "Cluster Identity Certainty" below) using at least two independent signals before performing any non-read-only actions. If credentials or integrations are not available, the agent will run a predefined passive diagnostic suite and flag findings as unverified.
- Verify: Execute read-only diagnostics autonomously and gather evidence (for example,
kubectl get events,kubectl -n <ns> describe pod <pod>, CNI-specific probes, andkubectl get networkpolicy -A). - Diagnose: Correlate collected data (events, logs, resource states, GitOps sync status) to identify probable root cause(s) and rank hypotheses by confidence.
- Triage: Prioritize issues by impact and urgency, and produce a remediation plan with clearly marked actions that are safe to run without human intervention.
- Remediate: When remediation is possible, the agent will either create GitOps PRs with diffs/tests or, apply scoped, reversible in-cluster changes. All write actions will be logged for audit.
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 · 83 lines · 61 tokens per session scan A 6f643b683874
Cluster Doctor is an agent published in the GitHub repository microsoftgbb/agentic-platform-engineering (71 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,579 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.