deploy-verification

deploy-verification is a skill for Claude Code from KhaledSaeed18/dotclaude. It costs 46 tokens per session (1,305 once invoked), scanned B, original, MIT.

A server-side checklist for proving that a production deployment works. It checks certificates, routing, containers, health probes, rolling updates, and the client addresses received by the backend.

In plain words
What is it for?
Use it to sign off a deployment, investigate dropped requests during an update, or check a proxy, certificate, header, or client-address setup.
Why use it?
A successful CI pipeline does not prove that the live service works from its actual server path. These checks provide command output as evidence and avoid misleading laptop network results.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the deploy plugin — 9 skills, 3 commands, 1 agent shipped together

Good fit Use it to sign off a deployment, investigate dropped requests during an update, or check a proxy, certificate, header, or client-address setup.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/khaledsaeed18/dotclaude/deploy-verification
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 KhaledSaeed18/dotclaude --skill deploy-verification
Clone the repo
git clone --depth 1 https://github.com/KhaledSaeed18/dotclaude

Made for: Claude Code.

Or install deploy, the plugin that ships this one along with the rest of its 9 skills, 3 commands, 1 agent.

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 deploy-verification

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

agentmods 80×15 button for deploy-verification

Your own site · 80×15
<a href="https://agentmods.dev/skills/khaledsaeed18/dotclaude/deploy-verification"><img src="https://agentmods.dev/badge/skills/khaledsaeed18/dotclaude/deploy-verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,305 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 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.00046 $0.01305
Opus 5.5 $0.00018 $0.00522
Sonnet 5.5 $0.00009 $0.00261
Haiku 4.5 $0.00005 $0.00130

Measured 11d ago against content hash f1d9b0a81b1f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

deploy-verification scanned grade B with 2 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 11d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

C=$(sudo docker ps --filter label=coolify.resourceName=<app> --format '{{.Names}}' | head -1)

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s -o /dev/null -w 'healthz %{http_code}\n' https://$D/healthz
.claude-plugin/plugins/deploy/skills/deploy-verification/SKILL.md · 69 lines

How it starts

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

A deploy is verified when the certificate verifies for the name, the container matches its contract, every public probe answers, a rolling update drops nothing, and the backend sees real client addresses. Measure from the server, not from a laptop: ISP paths produce false timeouts and hide proxy behaviour.

Hard rules: never break these

  • Probe from the server over one SSH connection (ControlMaster, see the coolify-vps-baseline skill). A laptop result is a hint, not evidence.
  • Read-only on production data. Open pages, call health routes, send probes to routes that do not exist; never submit a form or an action in a live app.
  • Never type credentials. When a signed-in check is needed, the owner signs in; you navigate.
  • A green pipeline is not a verified deploy. Read each job's conclusion and then run these checks anyway.
  • Report failures with their evidence, not "looks fine": the exact command and its output.

Step 1: Certificate and routing

D=app.example.com
echo | openssl s_client -connect 127.0.0.1:443 -servername $D -verify_hostname $D -verify_return_error 2>/dev/null | grep 'Verify return code'
echo | openssl s_client -connect 127.0.0.1:443 -servername $D 2>/dev/null | openssl x509 -noout -issuer -dates
curl -s -o /dev/null -w 'healthz %{http_code}\n' https://$D/healthz
curl -s -o /dev/null -w 'api ready %{http_code}\n' https://$D/api/v1/health/ready
curl -sI https://$D/ | grep -i -E '^(strict-transport|x-frame|content-security|x-powered|server)'

Verify return code: 0 (ok) and a Let's Encrypt issuer; TRAEFIK DEFAULT CERT means DNS did not exist when the router registered (redeploy after it does). Before DNS exists, add --resolve $D:443:127.0.0.1 -k to curl to test the route anyway. Compare the header set with the previous host's (curl -sI against it) so nothing an edge used to add is lost.

Step 2: Container contract

C=$(sudo docker ps --filter label=coolify.resourceName=<app> --format '{{.Names}}' | head -1)
sudo docker inspect "$C" --format 'health={{.State.Health.Status}} mem={{.HostConfig.Memory}} ports={{.HostConfig.PortBindings}} user={{.Config.User}} image={{.Config.Image}}'
sudo docker exec "$C" id -u

Read the full file on GitHub · 69 lines

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. 11d ago First seen · 69 lines · 46 tokens per session scan B f1d9b0a81b1f

Subscribe to this mod's changes

deploy-verification is a skill published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 1,305 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-05.

Related

Other skills, from other repositories

ast-grep

Searches and rewrites code by AST shape across 25 languages. Use when the target is a syntax pattern (every call/class/import shaped like X, a codemod, a YAML rule) rather than literal text; for plain strings, comments, or filenames, use rg.

code-yeongyu/oh-my-openagent · 61 tokens

debugging

Runs a hypothesis-driven debugging loop across any language or binary, escalating to orthogonal oracle angles and locking the fix with a failing test. Use for crashes, silent failures, hangs, wrong responses, memory leaks, async misbehavior, or reverse engineering.

code-yeongyu/oh-my-openagent · 53 tokens

lcx-doctor

Diagnose LazyCodex and Codex CLI installation health against the latest sources. Use whenever the user asks for a doctor or health check, says LazyCodex, lazycodex-ai, omo-codex, or Codex behaves oddly after an install, update, or config change, suspects a stale, drifted, or broken setup, or wants the local install…

code-yeongyu/oh-my-openagent · 93 tokens

lcx-report-bug

Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.

code-yeongyu/oh-my-openagent · 85 tokens

remove-deadcode

Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.

code-yeongyu/oh-my-openagent · 41 tokens

lsp

Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.

code-yeongyu/oh-my-openagent · 27 tokens