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/boparaiamrit/skills-by-amritWrote 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/boparaiamrit/skills-by-amrit/migrate)<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/migrate"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/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/boparaiamrit/skills-by-amrit/migrate"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/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.00014 | $0.00837 |
| Opus 5.5 | $0.00006 | $0.00335 |
| Sonnet 5.5 | $0.00003 | $0.00167 |
| Haiku 4.5 | $0.00001 | $0.00084 |
Grade A, and why
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 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/migrate — Migration Planning & Execution
Plan and execute database schema migrations or major code migrations with safety checks and rollback strategies.
Instructions
Step 1: Determine Migration Type
From $ARGUMENTS:
- Database migration — Schema changes (tables, columns, indexes, constraints)
- Code migration — Moving/renaming modules, updating patterns, API versioning
- Data migration — Transforming existing data (backfills, format changes)
- Infrastructure migration — Moving between services, upgrading runtimes
Step 2: Impact Analysis
# For database migrations — check current schema
# (Adapt to your ORM/migration tool)
npx prisma db pull 2>/dev/null
npx drizzle-kit introspect 2>/dev/null
cat schema.prisma 2>/dev/null | head -100
# For code migrations — find all affected files
grep -rn "[pattern-to-migrate]" --include="*.ts" --include="*.js" . | grep -v node_modules | wc -l
# Check what depends on the thing being migrated
grep -rn "import.*[module-name]" --include="*.ts" --include="*.js" . | grep -v node_modules
Step 3: Create Migration Plan
## Migration Plan: [Title]
### What's Changing
[Specific description of the migration]
### Pre-Migration Checklist
- [ ] Database backup exists
- [ ] All tests pass before migration
- [ ] Migration script tested on staging/dev
- [ ] Rollback script prepared and tested
- [ ] Downtime window communicated (if applicable)
### Migration Steps
1. [Step 1 — specific action]
2. [Step 2 — specific action]
3. [Step 3 — specific action]
### Rollback Steps (If Migration Fails)
1. [Rollback step 1]
2. [Rollback step 2]
3. [Rollback step 3]
### Affected Components
| Component | Impact | Risk |
|-----------|--------|------|
| [component] | [what changes] | Low/Med/High |
### Data Implications
- Rows affected: [estimate]
- Expected duration: [time]
- Data loss risk: None / Reversible / Irreversible
Step 4: Generate Migration Files
For database migrations, create the migration files using the project's migration tool:
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 · 142 lines · 14 tokens per session scan A 6abfacab298d
migrate is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 837 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-08-31.
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.batch_delete
Delete multiple JSON documents or paths in one itemwise batch.