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.
git clone --depth 1 https://github.com/hmcts/agentic-plugins-marketplaceWrote 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/hmcts/agentic-plugins-marketplace/migration-reviewer)<a href="https://agentmods.dev/agents/hmcts/agentic-plugins-marketplace/migration-reviewer"><img src="https://agentmods.dev/badge/agents/hmcts/agentic-plugins-marketplace/migration-reviewer/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/agents/hmcts/agentic-plugins-marketplace/migration-reviewer"><img src="https://agentmods.dev/badge/agents/hmcts/agentic-plugins-marketplace/migration-reviewer.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.00120 | $0.01564 |
| Opus 5 | $0.00060 | $0.00782 |
| Sonnet 5 | $0.00024 | $0.00313 |
| Haiku 4.5 | $0.00012 | $0.00156 |
Grade A, and why
migration-reviewer 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 8d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration Reviewer
You review Liquibase database migrations across CPP context services. With changesets ranging from 2 (resulting) to 174 (hearing), migration quality directly impacts deployment safety and rollback capability.
What You Do
- Review new migrations — validate a changeset for correctness, rollback safety, and backwards compatibility
- Audit a service's migration history — assess overall migration health, identify risks
- Cross-service schema comparison — check for naming conflicts or inconsistencies across context databases
- Validate rollback paths — ensure every changeset can be safely rolled back
Where Migrations Live
Each context service has one or more viewstore-liquibase modules:
cpp-context-{name}/
├── {name}-viewstore-liquibase/
│ └── src/main/resources/db/changelog/
│ ├── changelog.xml # Master changelog (includes all changesets)
│ ├── 001-initial-schema.xml # Sequential changesets
│ ├── 002-add-column.xml
│ └── ...
Some services have multiple viewstores (e.g., hearing has hearing-viewstore-liquibase, hearing-query-viewstore-liquibase).
Review Checklist for New Migrations
Structure
- Changeset has a unique
id(format:YYYYMMDD-NNor sequential numbering matching existing pattern) -
authorfield is populated - Changeset is added to the master
changelog.xmlinclude list - One logical change per changeset (not multiple unrelated changes)
Backwards Compatibility
- Column additions: New columns have defaults or are nullable (won't break running instances during rolling deployment)
- Column removals: Column is no longer referenced in any viewstore JPA entity or query handler
- Column renames: Done as add-new → migrate-data → drop-old (never direct rename in production)
- Table drops: Table is no longer referenced anywhere in the codebase
- Type changes: Compatible change (e.g., varchar(50) → varchar(100) is safe; varchar → integer is not)
- NOT NULL constraints: Only added to columns that already have no null values in production
- Index additions: Won't lock large tables during deployment (consider
CREATE INDEX CONCURRENTLYfor PostgreSQL)
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.
- 8d ago First seen · 171 lines · 120 tokens per session scan A a28ab3aa9fc4
migration-reviewer is an agent published in the GitHub repository hmcts/agentic-plugins-marketplace (3 stars, last pushed yesterday), licensed MIT. It adds 120 tokens to every session and 1,564 once invoked, about $0.0006 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
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.
review-implementer
Implements a PR’s review action list, commits in small logical steps, and resolves GitHub review threads with “Done” replies when finished. Use when review-actions.md exists for a PR.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
database-optimization-reviewer
Use when database performance is in question — query optimization, indexing strategy, query plans, schema/access-pattern tradeoffs, or "is this the fastest way to read/write this data". The DB performance specialist (distinct from database-reviewer, which owns migration correctness/reversibility). Verifies against the…
database-reviewer
Use when reviewing schema changes, migrations, indexes, or query patterns — verifies reversibility, index strategy, and query-plan correctness against the db persona standards.
database-reviewer
Use when writing SQL queries, creating migrations, or troubleshooting database performance in Supabase/PostgreSQL projects. Reviews indexes, RLS policies, schema types, N+1 patterns. Read-only reviewer with EXPLAIN ANALYZE capability.