deploy-verify
Reviewed
at commit d1db6fe
Checks configured live URLs after recognized deploy commands, waits for relevant GitHub Actions runs when present, and adds the verification result to model…
0 upvotes
Log in to upvote or save- Made by
- Yash Gadodia
- Pinned commit
-
d1db6fecdb7e2df54c402c3b02e0694829798eb8 - What we checked
-
After a Bash deploy command (git push, wrangler, vercel, fly, make deploy and similar) succeeds, it waits for the GitHub Actions run through gh and then fetches the live URL from your repo's .claude/deploy-verify.json with curl. It adds the result to the tool result so Claude cannot call the deploy verified without evidence, and may send one follow-up prompt if the check never passes. It stores nothing.
Review details
Static review of the source at the pinned commit; not run. Registers session.start (registers /deploy-verify), command.run, prompt.context (adds a deployVerify context block with the last verdict), turn.complete (releases a pending follow-up prompt) and tool.call on Bash, which only reacts to commands matching deploy patterns (quoted text, heredocs and dry runs are ignored) and appends advisory or verdict lines to the tool result context; it never denies a call. Runtime calls: $.process.run for curl (cache-busting GET of the configured URL), gh run list and git rev-parse, $.fs.read/exists for <repo>/.claude/deploy-verify.json and an optional matchFile, $.clock.after/every-style timers for polling (CI every 15s up to 20 minutes, live check every 15s for 3 minutes), $.ui.toast/status/log, $.prompt.submit for one follow-up prompt, and $.env.get for CLAUDE_MODS_DISABLE. The target URL comes from the repo's own config file, so a cloned repo can choose which URL is fetched after a push; only a GET with a cache-bust parameter is sent, no session data. A matchFile path may be absolute, and its first line is used as the string to look for. Errors are caught and reported as NOT VERIFIED context.
- What it uses
-
- Reads your prompts: no
- Sees tool calls: yes
- Blocks or changes tool calls: yes
- Reads or writes files: yes
- Runs programs on your machine: yes
- Calls the model (uses tokens): no
- Sends data over the network: yes
- Stores data: no
- Shows something on screen: yes
After a deploy command succeeds, curls the live URL with cache-busting and puts the verdict in the model's context, so a deploy cannot be claimed without evidence.
Made this mod? Add a badge to your README
Paste this into your README. The badge says reviewed once the current version has been reviewed, and links readers to this page.
[](https://modsforclaude.com/mods/deploy-verify/)