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/cutover)<a href="https://agentmods.dev/commands/khaledsaeed18/dotclaude/cutover"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/cutover/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/cutover"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/cutover.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.00035 | $0.00641 |
| Opus 5.5 | $0.00014 | $0.00256 |
| Sonnet 5.5 | $0.00007 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
cutover 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Request: $ARGUMENTS
Current DNS and deployment doc:
!D=$(echo "$ARGUMENTS" | awk '{print $1}'); [ -n "$D" ] && dig +noall +answer "$D" 2>/dev/null; dig +short NS "$(echo "$D" | awk -F. '{print $(NF-1)"."$NF}')" 2>/dev/null | head -2; ls docs/engineering/DEPLOYMENT.md 2>/dev/null
Task
Run the live-domain-cutover skill as a guided session. You verify; the owner edits DNS and hosting consoles from exact steps you give. Never advance a stage on an assumption: each stage ends with a verification whose output you show.
Stage 1: Record
Write the current record (type, value, TTL) and the authoritative servers into the deployment doc as the rollback value. Give the owner the TTL change (1 min on the existing record) and wait for "done"; confirm with dig @<ns>.
Stage 2: Rehearse
Give the owner the rehearsal record (<name>-next A to the new host, TTL 1 min). Deploy the app on that name only, then run the deploy-verification skill there in full, including a rolling-update probe and the header comparison with the old host. Fix and redeploy until every check passes. Report the checklist.
Stage 3: Switch
Agree a time. Give the owner the two edits (delete the old record, add the A record, TTL 1 min) and wait. Then: poll the authoritative server and two public resolvers; set the real domain as the only domain in Coolify and redeploy; watch the certificate until it verifies; switch the pipeline's probe variable; run deploy-verification on the real domain; ask the owner to reload their signed-in tab and confirm the session survived.
Stage 4: Soak and remove
Record the cutover time and results in the deployment doc. Ask the owner how long to soak. When they declare it over, give the removal steps (DNS cleanup and TTL back to Automatic, old host domain, Git connection and project, GitHub app access and environments, hook secrets in other repositories), verify each with dig, gh api and gh secret list, and finish the docs: migration section removed, follow-ups for other repositories listed.
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 · 38 lines · 35 tokens per session scan A 574c7570168d
cutover is a command published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 641 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
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
p6-audit-config
Checks security headers, CORS, DB access, secrets management, and server configuration.
support-model
Write a support model as Markdown in the user's repository. Produce designed HTML or PDF only when asked.
environment-switching-local-cloud-ssh
The environment selector at the bottom of Claude Code switches where work executes: local for fast interactive iteration, cloud (Anthropic servers) for routines that must run with your machine off, SSH for driving a remote box like a VPS.
design-doc
Write a design doc / RFC as Markdown in the user's repository. Use when invoked as /document-design-system:design-doc. Produce designed HTML or PDF only when asked.
evaluate
Execute Evaluate stage to validate generated framework artifacts.