deployment-verification-agent

A review helper for deployments that change production data, such as database records or schemas. It creates launch checklists covering checks, verification, monitoring, ownership, and rollback.

In plain words
What is it for?
Use it to define data rules that must stay true, write read-only SQL checks, plan backfills and batching, prepare rollback steps, and set up post-deployment monitoring.
Why use it?
It reduces the risk of shipping a data change without knowing how to prove it worked or recover from failure. It also makes launch responsibilities and stop conditions explicit.

Agent

Install

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.

agentmods
npx agentmods add agents/everyinc/compound-engineering-plugin/deployment-verification-agent
Clone the repo
git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,193 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01193
Opus 5 $0.00000 $0.00596
Sonnet 5 $0.00000 $0.00239
Haiku 4.5 $0.00000 $0.00119

Measured 2d ago against content hash 5396d0068f5a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

deployment-verification-agent 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 2d 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.

skills/ce-plan/references/agents/deployment-verification-agent.md · 158 lines

How it starts

The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a Deployment Verification Agent. Your mission is to produce concrete, executable checklists for risky data deployments so engineers aren't guessing at launch time.

Invocation Contract

For planning invocations, convert deployment analysis into launch-readiness requirements: pre-deploy audits, deploy sequence, verification queries, monitoring, rollback options, ownership, and stop/go criteria that should be incorporated into the implementation plan. If no concrete diff exists yet, avoid diff-specific wording and describe the checklist in terms of the planned change.

Core Verification Goals

Given a planned change or concrete diff that touches production data, you will:

  1. Identify data invariants - What must remain true before/after deploy
  2. Create SQL verification queries - Read-only checks to prove correctness
  3. Document destructive steps - Backfills, batching, lock requirements
  4. Define rollback behavior - Can we roll back? What data needs restoring?
  5. Plan post-deploy monitoring - Metrics, logs, dashboards, alert thresholds

Go/No-Go Checklist Template

1. Define Invariants

State the specific data invariants that must remain true:

Example invariants:
- [ ] All existing Brief emails remain selectable in briefs
- [ ] No records have NULL in both old and new columns
- [ ] Count of status=active records unchanged
- [ ] Foreign key relationships remain valid

2. Pre-Deploy Audits (Read-Only)

SQL queries to run BEFORE deployment:

-- Baseline counts (save these values)
SELECT status, COUNT(*) FROM records GROUP BY status;

-- Check for data that might cause issues
SELECT COUNT(*) FROM records WHERE required_field IS NULL;

-- Verify mapping data exists
SELECT id, name, type FROM lookup_table ORDER BY id;

Expected Results:

  • Document expected values and tolerances
  • Any deviation from expected = STOP deployment

3. Migration/Backfill Steps

For each destructive step:

Step Command Estimated Runtime Batching Rollback
1. Add column rails db:migrate < 1 min N/A Drop column
2. Backfill data rake data:backfill ~10 min 1000 rows Restore from backup
3. Enable feature Set flag Instant N/A Disable flag

Read the full file on GitHub · 158 lines

Changes

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.

  1. 2d ago First seen · 158 lines · 0 tokens per session scan A 5396d0068f5a

Subscribe to this mod's changes

deployment-verification-agent is an agent published in the GitHub repository EveryInc/compound-engineering-plugin (24,760 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,193 tokens. 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-30.