Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/TheLobbi/claudenpx agentmods add commands/thelobbi/claude/plugin-migrateWrote 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/commands/thelobbi/claude/plugin-migrate)<a href="https://agentmods.dev/commands/thelobbi/claude/plugin-migrate"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/plugin-migrate/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/commands/thelobbi/claude/plugin-migrate"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/plugin-migrate.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.00013 | $0.02092 |
| Opus 5.5 | $0.00005 | $0.00837 |
| Sonnet 5.5 | $0.00003 | $0.00418 |
| Haiku 4.5 | $0.00001 | $0.00209 |
Grade A, and why
plugin-migrate 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 2mo 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 — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Migration Management
Manage database migrations for Claude Code plugins with upgrade, downgrade, status checking, and migration creation.
Usage
/plugin-migrate <command> [options]
Commands
upgrade - Run pending migrations
Apply all pending migrations up to the latest or target version.
Syntax:
/plugin-migrate upgrade [target-version] [options]
Options:
[target-version]- Optional target version (default: latest)--dry-run- Show what would be migrated without executing--verbose- Show detailed migration output
Examples:
# Upgrade to latest
/plugin-migrate upgrade
# Upgrade to specific version
/plugin-migrate upgrade 2.0.0
# Dry run
/plugin-migrate upgrade --dry-run
# Verbose output
/plugin-migrate upgrade --verbose
Process:
- Load registered migrations
- Check current database version
- Determine pending migrations
- Execute migrations in order
- Track applied migrations in database
- Report results
downgrade - Rollback migrations
Rollback migrations by steps or to a target version.
Syntax:
/plugin-migrate downgrade [version|steps] [options]
Options:
[version]- Target version to downgrade to[steps]- Number of migrations to rollback (e.g.,1,3)--dry-run- Show what would be rolled back without executing--verbose- Show detailed rollback output
Examples:
# Rollback last migration
/plugin-migrate downgrade 1
# Rollback to version
/plugin-migrate downgrade 1.5.0
# Rollback 3 migrations
/plugin-migrate downgrade 3
# Dry run
/plugin-migrate downgrade 2 --dry-run
Process:
- Identify migrations to rollback
- Execute down() functions in reverse order
- Remove migration records from database
- Report results
status - Show migration status
Display the status of all registered migrations.
Syntax:
/plugin-migrate status [options]
Options:
--format=<format>- Output format:table,json,list(default: table)--pending-only- Show only pending migrations--applied-only- Show only applied migrations
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.
- 2mo ago First seen · 370 lines · 13 tokens per session scan A 33d276003dfb
plugin-migrate is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed 7d ago), licensed MIT. It adds 13 tokens to every session and 2,092 once invoked, about $0.0001 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-05.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
security
Scan a SQL string, .sql file, or SQL-building source file for injection risks with GoSQLX.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
new-migration
Scaffold a new database migration file pair (up + down) with auto-detection of migration tool and numbering.
json.batch_get
Read multiple JSON values by document and path.
json.index.drop
Drop a JSON secondary index by name.