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 gvkhosla/compound-engineering-pi --skill deployment-verification-agentgit clone --depth 1 https://github.com/gvkhosla/compound-engineering-piWrote 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/gvkhosla/compound-engineering-pi/deployment-verification-agent)<a href="https://agentmods.dev/skills/gvkhosla/compound-engineering-pi/deployment-verification-agent"><img src="https://agentmods.dev/badge/skills/gvkhosla/compound-engineering-pi/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/gvkhosla/compound-engineering-pi/deployment-verification-agent"><img src="https://agentmods.dev/badge/skills/gvkhosla/compound-engineering-pi/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.00040 | $0.01322 |
| Opus 5.5 | $0.00016 | $0.00529 |
| Sonnet 5.5 | $0.00008 | $0.00264 |
| Haiku 4.5 | $0.00004 | $0.00132 |
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 1mo 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 — 174 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;
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.
- 1mo ago First seen · 174 lines · 40 tokens per session scan A ea7f869f9208
deployment-verification-agent is a skill published in the GitHub repository gvkhosla/compound-engineering-pi (52 stars, last pushed 15d ago), licensed MIT. It adds 40 tokens to every session and 1,322 once invoked, about $0.0002 per session on Opus 5.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-15.
Other skills, from other repositories
pi-package-sandbox-test
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
pi-primitive-check
Use when evaluating proposed Pi customisation work against built-in Pi primitives before implementation, especially extensions, packages, slash commands, and workflow ideas.
pi-observability-local-dev
Use when developing or reviewing packages/pi-observability dashboard/server changes locally, especially rebuilding dist, restarting the 43190 server, validating UI behavior, or keeping the local dashboard in sync with source edits.
review-harness
Use when reviewing implementation work that ran through a /tmp Pi task harness. Checks contract drift, unsafe shortcuts, validation evidence, and status honesty.
pi
Use when needing a minimal, extensible terminal AI coding agent harness in TypeScript with plugin architecture. Pi: minimalist terminal AI coding agent emphasizing simplicity and composability.
memory-layer
Standalone persistent memory for Pi — smart search, symbol clustering, dedup, auto-recovery, trust scoring. Zero Python dependency.