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 mitodl/agent-kit --skill deploy-verificationgit clone --depth 1 https://github.com/mitodl/agent-kitWrote 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/mitodl/agent-kit/deploy-verification)<a href="https://agentmods.dev/skills/mitodl/agent-kit/deploy-verification"><img src="https://agentmods.dev/badge/skills/mitodl/agent-kit/deploy-verification/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/mitodl/agent-kit/deploy-verification"><img src="https://agentmods.dev/badge/skills/mitodl/agent-kit/deploy-verification.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.00127 | $0.01711 |
| Opus 5.5 | $0.00051 | $0.00684 |
| Sonnet 5.5 | $0.00025 | $0.00342 |
| Haiku 4.5 | $0.00013 | $0.00171 |
Grade A, and why
deploy-verification 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 15d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Verification
A config or manifest change merging is not the same as it taking effect. Three separate things can each silently fail while the previous one succeeds: the CD pipeline can be pending or red, the pods can never actually restart even though the pipeline ran, and the restarted pods can still be running the old value if the change didn't reach the path you think it did. This skill walks all three, in order, and demands evidence at each step rather than inferring success from the step before it.
Core rule: report pass/fail per step with the raw evidence (a pod age, a rollout status, a query result, a preview diff) — "looks deployed" or "should be live now" is not a verification, it's a guess with better formatting. If a step can't be checked (no cluster access, no query result yet), say so explicitly rather than skipping it silently.
Step 1 — Confirm the CD pipeline ran and succeeded
Find the deploy workflow for the merged PR's repo and confirm a run completed after the merge commit landed, not just that one exists:
gh run list -R <owner>/<repo> --workflow <deploy-workflow>.yml --limit 5 \
--json databaseId,status,conclusion,headSha,createdAt
Match headSha (or the commit it built from) against the actual merge SHA
— a run against a stale SHA doesn't cover this change. status: in_progress
means wait and re-check, not "probably fine." A conclusion: failure stops
here: the change never reached the cluster, and nothing past this step is
worth checking yet.
Step 2 — Confirm the pods actually rolled
A green pipeline only means the deploy step ran, not that the workload picked it up. Check pod age against the deploy time:
kubectl get pods -n <namespace> -l app=<app> -o wide
kubectl rollout status deployment/<name> -n <namespace> --timeout=5m
Always bound rollout status with --timeout. Its default is --timeout=0s,
which kubectl documents as "zero means never" — an unbounded watch, so a
stalled rollout hangs the verification instead of reporting anything. A
non-zero exit on timeout is itself a finding: the rollout did not complete
within the window, which is exactly the "looks deployed but isn't" case this
checklist exists to catch. Report it as a failed step, not as a flaky command
to retry with a longer wait.
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.
- 15d ago Changed 67660c4a8457
- 1mo ago First seen · 159 lines · 127 tokens per session scan A d027b706ca6f
deploy-verification is a skill published in the GitHub repository mitodl/agent-kit (5 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 127 tokens to every session and 1,711 once invoked, about $0.0005 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".