Borrowing it
Nothing to install: this file belongs to creator35lwb-web/VerifiMind-PEAS. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/creator35lwb-web/VerifiMind-PEAS/main/.claude/commands/verifimind-deploy.mdgit clone --depth 1 https://github.com/creator35lwb-web/VerifiMind-PEASWrote 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/creator35lwb-web/verifimind-peas/verifimind-deploy)<a href="https://agentmods.dev/commands/creator35lwb-web/verifimind-peas/verifimind-deploy"><img src="https://agentmods.dev/badge/commands/creator35lwb-web/verifimind-peas/verifimind-deploy/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/creator35lwb-web/verifimind-peas/verifimind-deploy"><img src="https://agentmods.dev/badge/commands/creator35lwb-web/verifimind-peas/verifimind-deploy.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.00023 | $0.00538 |
| Opus 5 | $0.00012 | $0.00269 |
| Sonnet 5 | $0.00005 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
verifimind-deploy 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 10d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/verifimind-deploy
This public command is a recovery wrapper, not a second release recipe. Normal production releases use the Cloud Build trigger created by an authorized merge. That trigger already counts as the one deployment execution; do not run this command after it starts or succeeds.
The private Command Central release orchestrator owns review, authorization, provenance, smoke, Release, registry, post-deploy truth, and the private receipt. This repository owns the executable recovery carrier.
Use only for an authorized recovery
Run the recovery carrier only when the normal trigger is unavailable or failed before producing an acceptable serving artifact, and Alton has authorized recovery from an exact reviewed merge.
Before execution, prove all of the following:
- this checkout is
creator35lwb-web/VerifiMind-PEAS; HEADis the exact authorized merge on currentorigin/main;- the worktree is clean, including untracked files;
- the intended version matches every discovered version assertion;
- the current serving revision and rollback source are recorded;
- no merge-trigger deployment for the same release is still running.
Execute one canonical carrier
cd mcp-server
./deploy-cloudrun.sh
Do not reproduce or bypass the carrier's build, source-archive, image-identity, or Cloud Run commands. If a guard fails closed, repair the cause and rebind the authorization to any changed SHA.
Required verification
After the single recovery execution:
- Bind the source merge, build ID, immutable image identity, serving revision, traffic percentage, and rollback target.
- Verify
/health,/setup, and the server card agree on version, availability, routing, protocol, and failover semantics. - Run the versioned external smoke oracle and record PASS / STOP / INSTRUMENT separately.
- Prepare exact deployment facts through a bounded docs-only truth PR. Do not
push directly to public
mainor to the live Wiki. - Complete the GitHub Release, registry, and private receipt only through the Command Central release gate.
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.
- 10d ago First seen · 67 lines · 23 tokens per session scan A d9052d6baf00
verifimind-deploy is a command published in the GitHub repository creator35lwb-web/VerifiMind-PEAS (2 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 538 once invoked, about $0.0001 per session on Opus 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-08-31.
Other commands, from other repositories
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.