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/mickelsamuel/migrationpilotWrote 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/plugins/mickelsamuel/migrationpilot/claude-code)<a href="https://agentmods.dev/plugins/mickelsamuel/migrationpilot/claude-code"><img src="https://agentmods.dev/badge/plugins/mickelsamuel/migrationpilot/claude-code/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/plugins/mickelsamuel/migrationpilot/claude-code"><img src="https://agentmods.dev/badge/plugins/mickelsamuel/migrationpilot/claude-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
migrationpilot 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.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "migrationpilot",
"displayName": "MigrationPilot",
"version": "1.5.1",
"description": "Blocks unsafe PostgreSQL migrations before they are written or run. Adds a migration-safety skill and a PreToolUse guardrail hook.",
"author": {
"name": "Mickel Samuel",
"email": "[email protected]",
"url": "https://github.com/mickelsamuel"
},
"homepage": "https://migrationpilot.dev",
"repository": "https://github.com/mickelsamuel/migrationpilot",
"license": "MIT",
"keywords": [
"postgresql",
"postgres",
"migration",
"database",
"safety",
"guardrail",
"zero-downtime",
"ddl"
],
"hooks": "./hooks/hooks.json"
}
What it installs
The manifest is a name and a version. 1 skill, 1 hook travel with it, and installing the plugin installs all of them — 119 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 27 lines scan A d493a472df4c
migrationpilot is a plugin published in the GitHub repository mickelsamuel/migrationpilot (9 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
alloydb
Create, connect, and interact with an AlloyDB for PostgreSQL database and data.
alloydb
Create, connect, and interact with an AlloyDB for PostgreSQL database and data.
slop-chop
Chop AI writing tells out of text. Wraps the slop-chop CLI so Claude can strip em-dashes, semicolons, and buzzwords, enforce a spelling dialect, or run the model rewrite pass on a draft.
alloydb-omni
Create, connect, and interact with an AlloyDB Omni database and data.
alloydb-omni
Create, connect, and interact with an AlloyDB Omni database and data.
nlqdb-memory
Persistent, queryable memory for your agent: a real Postgres it asks in plain English over MCP, so it can GROUP BY / JOIN / aggregate over what it remembered instead of recalling the nearest few rows. Bundles the hosted MCP server plus two skills that teach the agent when to use it.