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.
git clone --depth 1 https://github.com/KhaledSaeed18/dotclaudeWrote 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/commands/khaledsaeed18/dotclaude/deploy-verify)<a href="https://agentmods.dev/commands/khaledsaeed18/dotclaude/deploy-verify"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/deploy-verify/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/commands/khaledsaeed18/dotclaude/deploy-verify"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/deploy-verify.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.00037 | $0.00559 |
| Opus 5.5 | $0.00015 | $0.00224 |
| Sonnet 5.5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
deploy-verify 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 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.
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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Request: $ARGUMENTS
Deployment doc and latest main run:
!ls docs/engineering/DEPLOYMENT.md docs/*deploy* 2>/dev/null; gh run list --branch main --limit 1 --json databaseId,conclusion,displayTitle --jq '.[] | "\(.databaseId) \(.conclusion) \(.displayTitle)"' 2>/dev/null
Task
Run the deploy-verification skill end to end for the given domain and report a checklist. Everything is read-only and measured from the server over one SSH connection; the owner's signed-in session is used only to open pages.
- Resolve the inputs from the arguments or the deployment doc: domain, SSH alias, Coolify resource names of the app and of the API behind it. Ask only for what cannot be found.
- Open the SSH ControlMaster connection once; every later command multiplexes through it.
- Run the checks in this order, each with its command and output captured: certificate verification and issuer;
/healthzand the API readiness route through the domain; response headers (and a diff against the previous host when one is named); container contract (health, memory limit, no port bindings, non-root, image tag equals the latest publishedsha-tag); client address proof with a forged header from the server and from this machine; when--runis given and its deploy job has not started, arm the rolling-update probe and summarise the status counts and the slowest response. - If the owner is signed in on the domain in the browser pane, open the landing page, one data page and one page per locale and read the network log for same-origin API calls and their status codes. Click nothing that writes.
- Close the SSH master connection.
Produce a table: check, command, expected, observed, pass or fail. End with the overall verdict and, for every failure, the skill that fixes it (nextjs-coolify-image for shutdown or headers, coolify-image-app for container settings, proxy-client-address for the address, live-domain-cutover for certificate and DNS). Offer to append the dated table to the deployment doc.
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.
- 11d ago First seen · 28 lines · 37 tokens per session scan A 22cbc24a044a
deploy-verify is a command published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 559 once invoked, about $0.0001 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-10-05.
Other commands, from other repositories
bugfix
IMPORTANT: You MUST run this shell command FIRST before doing anything else.
refactor-clean
Refactor code for readability and maintainability using clean code and SOLID principles.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.