agentmods.dev

verify-apply

verify-apply is a skill for Claude Code from confighub/confighub-skills. It costs 51 tokens per session (1,836 once invoked), scanned A, original, MIT.

A read-only checklist for confirming that a published ConfigHub release reached its controller and running cluster.

In plain words
What is it for?
It is for checking the exact release, its content and manifest identifiers, controller synchronization, and runtime convergence after deployment.
Why use it?
A successful release publication alone does not prove that the application is live, so it traces the release through each delivery stage.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the confighub-skills plugin — 16 skills, 1 command, 1 hook shipped together

not rated 2repo changed yesterday A scan 51 tokens original MIT

Good fit It is for checking the exact release, its content and manifest identifiers, controller synchronization, and runtime convergence after deployment.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/confighub/confighub-skills/verify-apply
View source ↗ confighub/confighub-skills
Install

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.

Any agent
npx skills add confighub/confighub-skills --skill verify-apply
Clone the repo
git clone --depth 1 https://github.com/confighub/confighub-skills

Made for: Claude Code.

Or install confighub-skills, the plugin that ships this one along with the rest of its 16 skills, 1 command, 1 hook.

Wrote 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.

agentmods badge for verify-apply

README.md
[![agentmods](https://agentmods.dev/badge/skills/confighub/confighub-skills/verify-apply/github.svg)](https://agentmods.dev/skills/confighub/confighub-skills/verify-apply)
Your own site
<a href="https://agentmods.dev/skills/confighub/confighub-skills/verify-apply"><img src="https://agentmods.dev/badge/skills/confighub/confighub-skills/verify-apply/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.

agentmods 80×15 button for verify-apply

Your own site · 80×15
<a href="https://agentmods.dev/skills/confighub/confighub-skills/verify-apply"><img src="https://agentmods.dev/badge/skills/confighub/confighub-skills/verify-apply.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,836 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.01836
Opus 5 $0.00026 $0.00918
Sonnet 5 $0.00010 $0.00367
Haiku 4.5 $0.00005 $0.00184

Measured yesterday against content hash 49d4cc5a0ed4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

verify-apply 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 yesterday.

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.

skills/verify-apply/SKILL.md · 119 lines

How it starts

The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.

verify-apply

Execution mode: follow references/execution-modes.md. This Skill itself is read-only and grants no automatic tool permission. Run scoped proof reads through the host's normal permission flow; route a requested fix to its owning mutation Skill.

Prove the current delivery chain, read-only: ConfigHub intent → immutable Space Release → controller source/sync → runtime target. A successful publish alone is not a live deployment.

Read the exact release

Start with the Release ID, bundle Digest, and OCI ManifestDigest captured by the successful publish. These are different fields:

  • Digest identifies the bundle content;
  • ManifestDigest identifies the OCI manifest the controller consumes; and
  • ReleaseID identifies the ConfigHub Release record.

Prefer an immutable selector:

cub release get --space <variant-space> <release-id>
cub release get --space <variant-space> --oci-reference sha256:<manifest-digest>
cub release get --space <variant-space> --bundle-digest sha256:<bundle-digest>

If only the Space is known, discover the newest Release with the weaker selector:

cub release get --space <variant-space> --oci-reference latest

Record the SpaceID/slug, ReleaseID/number, UnitCount, TagID if any, bundle Digest, ManifestDigest, repository/reference, and creation time. Do not infer provenance from an invented release-link field. If the user needs a previous immutable release, use its captured ID or digest; never silently substitute latest.

The public Release resource exposes no TargetID or stored OCI Manifest. The last source-reviewed v0.2.11 profile put com.confighub.target.id in the generated manifest committed by ManifestDigest; exact v0.2.21 implementation is not source-reviewed here. Historical Target proof therefore needs a digest-matching publication/registry receipt. Today's Space.ReleaseTargetID is current state only.

Recover the historical manifest—never substitute today's set

Read the full file on GitHub · 119 lines

Files

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.

Changes

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.

  1. yesterday Changed 49d4cc5a0ed4
  2. 11d ago First seen · 119 lines · 51 tokens per session scan A 11ce12a27eef

Subscribe to this mod's changes

verify-apply is a skill published in the GitHub repository confighub/confighub-skills (2 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 1,836 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-31.

CloudDevOps and cloud
Related

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…

google/skills · 83 tokens

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 disaster recovery setup or full cluster backups (use gke-backup-dr instead).

google/skills · 73 tokens

gke-workload-security

Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…

google/skills · 181 tokens

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".

microsoft/skills · 78 tokens

nemo-automodel-launcher-config

Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.

NVIDIA/skills · 30 tokens

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…

Jeffallan/claude-skills · 71 tokens