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 skills/smana/cloud-native-ref/verify-specnpx skills add Smana/cloud-native-ref --skill verify-specgit clone --depth 1 https://github.com/Smana/cloud-native-refWhat 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.00052 | $0.01479 |
| Opus 5 | $0.00026 | $0.00740 |
| Sonnet 5 | $0.00010 | $0.00296 |
| Haiku 4.5 | $0.00005 | $0.00148 |
Grade A, and why
verify-spec 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Spec Skill
Close the acceptance loop. Merged work is not "done" until the design's success criteria are observably met in the target cluster.
Workflow
1. Locate inputs
Resolve $ARGUMENTS to a design document under docs/superpowers/specs/. Accept a bare topic
slug and glob for it. Abort with guidance if not found.
Read:
- the design doc — its goals, its Testing table, and any explicit success criteria
- the matching plan at
docs/superpowers/plans/<same-date>-<same-topic>-plan.md, if present — its per-task verification commands are usually the best evidence source - any example manifests the design names
Archived specs under docs/specs/done/ are also accepted, for re-verifying older work. Those use
the retired SC-XXX format; parse **SC-XXX**: <text> lines when you see them.
2. Enumerate success criteria
Superpowers designs state criteria in prose and in a Testing table rather than as numbered
SC-XXX items. Extract one checkable claim per row or per bullet, and give each a stable local
id (C-1, C-2, …) for the report. For each, infer a verification method:
| Criterion pattern | Verification method |
|---|---|
| "pods can call AWS APIs …" | kubectl run a test pod; try the API; check result |
| "reconciliation succeeds within Xs" | flux get + time window check |
| "metrics emit" | VictoriaMetrics query for the metric name |
| "logs appear" | VictoriaLogs query for the log stream |
| "latency p95 < Y" | VictoriaMetrics histogram_quantile(0.95, ...) |
| "eviction deterministic" | deploy, fill, observe eviction counter |
| "resource X created" | kubectl get X -l <label> |
| a literal shell command in the Testing table | run it verbatim; compare to the stated expected output |
If the method is unclear, list the criterion as MANUAL and ask the user how they want to verify.
3. Deploy the example (idempotent)
Prefer kubectl apply -k <dir>/examples/ or kubectl apply -f <dir>/examples/<name>.yaml. If the resource is a Flux HelmRelease / Kustomization, just wait for reconciliation — Flux owns deployment.
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 · 144 lines · 52 tokens per session scan A 40b46b0787e2
verify-spec is a skill published in the GitHub repository Smana/cloud-native-ref (99 stars, last pushed 2d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,479 once invoked, about $0.0003 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-30.
Other skills, from other repositories
geoserver-cloud
Use when deploying GeoServer on Kubernetes as cloud-native microservices with auto-scaling, service discovery, and centralized configuration. GeoServer Cloud: break monolithic GeoServer into independently scalable WMS/WFS/WCS services.
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.
kubernetes-agent
Kubernetes production patterns — manifests, resource sizing, health probes, scaling, secrets, networking, and troubleshooting.
container-security
Performs a container and Kubernetes security review against the CIS Docker Benchmark v1.6.0, CIS Kubernetes Benchmark v1.9.0, and NIST SP 800-190. Auto-invoked when reviewing Dockerfiles, Kubernetes manifests, Helm charts, or container orchestration configurations. Evaluates image security, runtime hardening, RBAC…
r00-anthropics-skills--devops
☁️ DevOps & Cloud Infrastructure skill suite derived from anthropics/skills. CI/CD pipelines, container orchestration, IaC, monitoring and incident response. Provides 10 specialised commands for devops, cloud, docker workflows.
r00-vincenthopf-My-Claude-Code--devops
☁️ DevOps & Cloud Infrastructure skill suite derived from vincenthopf/My-Claude-Code. CI/CD pipelines, container orchestration, IaC, monitoring and incident response. Provides 10 specialised commands for devops, cloud, docker workflows.