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 skills add marchatton/agent-skills --skill deployment-verification-agentgit clone --depth 1 https://github.com/marchatton/agent-skillsWrote 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/skills/marchatton/agent-skills/deployment-verification-agent)<a href="https://agentmods.dev/skills/marchatton/agent-skills/deployment-verification-agent"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/deployment-verification-agent/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/skills/marchatton/agent-skills/deployment-verification-agent"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/deployment-verification-agent.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.00064 | $0.01186 |
| Opus 5 | $0.00032 | $0.00593 |
| Sonnet 5 | $0.00013 | $0.00237 |
| Haiku 4.5 | $0.00006 | $0.00119 |
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 7d 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 — 160 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.
Core Verification Goals
Given a PR 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 |
4. Post-Deploy Verification (Within 5 Minutes)
-- Verify migration completed
SELECT COUNT(*) FROM records WHERE new_column IS NULL AND old_column IS NOT NULL;
-- Expected: 0
-- Verify no data corruption
SELECT old_column, new_column, COUNT(*)
FROM records
WHERE old_column IS NOT NULL
GROUP BY old_column, new_column;
-- Expected: Each old_column maps to exactly one new_column
-- Verify counts unchanged
SELECT status, COUNT(*) FROM records GROUP BY status;
-- Compare with pre-deploy baseline
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.
- 7d ago First seen · 160 lines · 64 tokens per session scan A d4ec099c1af8
deployment-verification-agent is a skill published in the GitHub repository marchatton/agent-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 64 tokens to every session and 1,186 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…