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 skills add agenticdevops/aoh --skill pending-pod-triagegit clone --depth 1 https://github.com/agenticdevops/aohWrote 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/skills/agenticdevops/aoh/pending-pod-triage)<a href="https://agentmods.dev/skills/agenticdevops/aoh/pending-pod-triage"><img src="https://agentmods.dev/badge/skills/agenticdevops/aoh/pending-pod-triage/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/skills/agenticdevops/aoh/pending-pod-triage"><img src="https://agentmods.dev/badge/skills/agenticdevops/aoh/pending-pod-triage.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.00044 | $0.00245 |
| Opus 5.5 | $0.00018 | $0.00098 |
| Sonnet 5.5 | $0.00009 | $0.00049 |
| Haiku 4.5 | $0.00004 | $0.00024 |
Grade A, and why
pending-pod-triage 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 1mo 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
Pending Pod Triage
Find why a pod is unschedulable. Read-only — RBAC limits this agent to get/list/watch.
Process
- Run
scripts/collect_pending_pod_diagnostics.sh(no args) to list Pending pods. - For a specific pod:
scripts/collect_pending_pod_diagnostics.sh <namespace> <pod>. - Read the FailedScheduling event first — it names the constraint:
- "Insufficient cpu/memory" → compare requests to node allocatable in the output
- "node(s) had untolerated taint" → compare taints to the pod's tolerations
- "unbound immediate PersistentVolumeClaims" → check the PVC section
- No nodes at all / network not ready → node-level problem: switch to the node-notready-triage skill
- Recommend the smallest safe next action with the exact evidence line.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 21 lines · 44 tokens per session scan A 79fbbd992de0
pending-pod-triage is a skill published in the GitHub repository agenticdevops/aoh (6 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 245 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 skills, from other repositories
harness
Use when governing a workspace's control plane, code or not — the 01-TOOLS/ tooling layer, the 02-DOCS/ chaos→knowledge wiki, the root Knowledge map. Audits it, migrates legacy XX- folders, scaffolds provider tooling, sweeps the inbox, eats a file the person hands over ("cómete este fichero", "guárdalo en la…
vigilante-issue-implementation-on-kubernetes
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Kubernetes-focused repository with manifest hardening and workload security guidance.
docker-compose-launch
Launch worktree-scoped local services for issue implementation when a monorepo skill requires database dependencies.
container-manager-kubernetes-operations
Full operational Kubernetes surface via the container-manager-mcp MCP server — workloads (pods/rollouts/StatefulSets/DaemonSets/ReplicaSets/Jobs/CronJobs), config (ConfigMaps/Secrets/Namespaces/CRDs/patch), networking (Ingress/native Services/NetworkPolicy/DNS), storage (PV/PVC/StorageClass/snapshots/CSI), RBAC…
vigilante-issue-implementation-on-docker
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Docker-focused repository with Dockerfile best practices, image hardening, and secret-safe build guidance.
bdbsaashost
Use when operating the BDB Multi-Cloud Fleet. Governs Primary Compute, GCP Identity, Oracle, FastMCP SSE Gateway, 4-Eyes Approvals, agent-sudo guardrails, Incus containers, and LLDAP/Authelia identity management.