deploy-verify

Not yet reviewed

Checks configured live URLs after recognized deploy commands, waits for relevant GitHub Actions runs when present, and adds the verification result to model…

Source

github.com/yash-gadodia/claude-mods/tree/main/deploy-verify

Made by

Yash Gadodia

Pinned commit

No commit pinned yet

Review notes

Listed from the community catalogue awesome-claude-code-mods (https://github.com/karanb192/awesome-claude-code-mods) on 2026-10-06. Not reviewed by modsforClaude.com yet: the hooked events and what it uses come from that catalogue's automated scan of the source.

What a scan found

Reads your prompts
Sees tool calls
Reads or writes files
Runs programs on your machine
Calls the model (uses tokens)
Shows something on screen

Reported by an automated scan of the source, not checked by a person yet.

Hooked events

How to install

This mod is not in the official Claude directory, so you load it straight from its source on GitHub. modsforClaude.com is an unofficial community site: we do not host, repackage or install anything. Read the source and the review on this page first.

In the terminal

Clone the repository and start Claude Code with the mod. It stays loaded for that session.

git clone https://github.com/yash-gadodia/claude-mods
claude --plugin-dir ./claude-mods/deploy-verify

In the desktop app

Clone the repository into a folder you keep:

git clone https://github.com/yash-gadodia/claude-mods ~/claude-mods/claude-mods

Add that folder to CLAUDE_CODE_PLUGIN_DIRS in the env block of ~/.claude/settings.json, then start a new session in the Code tab. On Windows, with your own user name:

"env": {
  "CLAUDE_CODE_PLUGIN_DIRS": "C:\\Users\\you\\claude-mods\\claude-mods\\deploy-verify"
}

On macOS and Linux:

"env": {
  "CLAUDE_CODE_PLUGIN_DIRS": "~/claude-mods/claude-mods/deploy-verify"
}

Already loading other mods this way? Add the folder to the same value, separated by ; on Windows or : on macOS and Linux.

Not working, or want to change its settings? How to load a Claude Code mod walks through every step.

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.