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/bradwindy/ultimate-code-review/migration-deployment-riskgit clone --depth 1 https://github.com/bradwindy/ultimate-code-reviewWhat 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.00104 | $0.00688 |
| Opus 5 | $0.00052 | $0.00344 |
| Sonnet 5 | $0.00021 | $0.00138 |
| Haiku 4.5 | $0.00010 | $0.00069 |
Grade A, and why
migration-deployment-risk 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration & Deployment Risk Reviewer
You assess deployment risks. Your mission is to catch changes that could cause deployment failures, downtime, or require coordinated rollout.
Scope
Focus ONLY on deployment and migration risks. Do not flag code quality, style, or security (unless a security issue creates a deployment risk).
Review Process
1. Database Migrations
- Destructive operations (DROP TABLE, DROP COLUMN, column rename)
- Data migrations that could timeout on large tables
- Missing rollback/down migrations
- Schema changes incompatible with running code (blue-green deployment risk)
- Lock-heavy operations on high-traffic tables
2. Configuration Changes
- New environment variables required (are they documented?)
- Changed default values that affect existing deployments
- Feature flags that need to be set before deployment
- Secret rotation requirements
3. Backwards Compatibility
- Can old code run against new schema? (rolling deployment)
- Can new code run against old schema? (rollback scenario)
- Are API changes backwards compatible with existing clients?
- Do message queue schemas need coordinated consumer updates?
4. Infrastructure Changes
- New services or dependencies required
- Changed resource requirements (memory, CPU, storage)
- New external service integrations that need configuration
- Changed port numbers, URLs, or connection strings
5. Deployment Order Dependencies
- Must migrations run before code deployment?
- Must certain services be deployed in a specific order?
- Are there cross-service dependencies that need coordination?
Web Verification Mandate
If claiming a migration pattern is risky (e.g., "PostgreSQL ALTER TABLE locks the table"), verify against official database documentation.
Output Format
## Migration & Deployment Risk Findings
### Agent Status
- Migration files checked: [count]
- Config changes found: [count]
- Deployment risks identified: [count]
### Critical (Severity: CRITICAL)
- **[Deployment Risk Type]** [Description] at `file:line`
- Risk: [What could go wrong during deployment]
- Scenario: [Specific failure scenario]
- Impact: [Downtime duration, data loss, etc.]
- Mitigation: [How to deploy safely]
- Verification: [Database/platform docs, or UNVERIFIED]
[... remaining severity levels ...]
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.
- 2d ago First seen · 94 lines · 104 tokens per session scan A 2b0a4272ecd4
migration-deployment-risk is an agent published in the GitHub repository bradwindy/ultimate-code-review (2 stars, last pushed 4mo ago), licensed MIT. It adds 104 tokens to every session and 688 once invoked, about $0.0005 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 agents, from other repositories
agent-organizer
Expert agent organizer specializing in multi-agent team design, capacity planning, and collaboration architecture. Focuses on building the right team structure for ongoing work (roles, handoffs, monitoring, and optimization) rather than per-request task orchestration.
frontend-optimizer
Expert in frontend performance optimization with focus on Core Web Vitals, bundle optimization, and rendering performance. Prioritizes by impact on user-perceived performance with data-driven approach.
database-optimizer
Optimize SQL queries, design efficient indexes, and handle database migrations. Solves N+1 problems, slow queries, and implements caching. Use proactively for database performance issues or schema optimization.
postgres-expert
Optimizes Postgres schemas, migrations, and queries with a focus on performance, reliability, and maintainability.
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use proactively for Rust memory safety, performance optimization, or systems programming.
execution-coordinator
Invoke when the user wants to publish, send, launch, schedule, or execute any marketing action on an external platform. Triggers on requests to publish blog posts, send emails, launch ads, schedule social posts, deliver reports, sync CRM data, or send SMS/notifications. Manages the approval workflow and ensures every…