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.
npx agentmods add agents/ronronner02/codepilot-agent/deployment-verification-agentgit clone --depth 1 https://github.com/ronronner02/codepilot-agentWrote 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/agents/ronronner02/codepilot-agent/deployment-verification-agent)<a href="https://agentmods.dev/agents/ronronner02/codepilot-agent/deployment-verification-agent"><img src="https://agentmods.dev/badge/agents/ronronner02/codepilot-agent/deployment-verification-agent.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01281 |
| Opus 5 | $0.00000 | $0.00641 |
| Sonnet 5 | $0.00000 | $0.00256 |
| Haiku 4.5 | $0.00000 | $0.00128 |
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 yesterday.
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 — 161 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:
- Identify data invariants - What must remain true before/after deploy
- Create SQL verification queries - Read-only checks to prove correctness
- Document destructive steps - Backfills, batching, lock requirements
- Define rollback behavior - Can we roll back? What data needs restoring?
- 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 |
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.
- yesterday First seen · 161 lines · 0 tokens per session scan A e90eaab26736
deployment-verification-agent is an agent published in the GitHub repository ronronner02/codepilot-agent (0 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,281 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-09-03.
Other agents, from other repositories
backend-engineer
Backend implementation. Use for API, authentication, DB migration work.
db-engineer
Database design and implementation specialist. Use for schema, ERD, migration, query tuning, vector DB work.
workflow-architect
Multi-agent workflow: LangGraph pipelines, supervisor-worker patterns, state/checkpointing, RAG orchestration.
db-migration-reviewer
Database migration safety specialist. Activates when migrations/ files are detected in a PR or feature branch. Checks lock duration, rollback strategy, zero-downtime patterns, PII column handling, and index creation safety. Writes docs/migrations/MIGRATE-{slug}.md. Blocks deploy if no rollback path exists.
dog
You are a Dolt maintenance worker for the dolt pack. Your work is limited to Dolt operational formulas assigned to this session or routed to the Dolt dog pool.
deploy-engineer
Runs and verifies deployments for the agency's two client stacks — BigCorp on AWS (Terraform, Lambda, RDS) and StartupXYZ on Vercel — including CI pipelines, migrations, and secret management. Spawn for deploy execution, rollback prep, or infrastructure checks.