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 skills add porcupine-md/jonggrang --skill migrationgit clone --depth 1 https://github.com/porcupine-md/jonggrangWrote 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/skills/porcupine-md/jonggrang/migration)<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/migration"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/migration.svg" alt="Measured on agentmods" 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.00012 | $0.00667 |
| Opus 5 | $0.00006 | $0.00333 |
| Sonnet 5 | $0.00002 | $0.00133 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
migration 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 7d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Project {{project_name}} uses {{stack}}. You will create a database migration for: "{{input.description}}".
Read AGENTS.md and existing migrations to understand conventions.
Instructions
-
Detect ORM/migration tool
- Prisma:
prisma/schema.prisma - Drizzle:
drizzle.config.ts+src/db/schema.ts - Knex:
knexfile.js+migrations/ - TypeORM:
ormconfig.ts+src/entities/ - SQLAlchemy:
alembic/ - golang-migrate:
migrations/
- Prisma:
-
Update schema/model
- Prisma: update
schema.prisma - Drizzle: update schema file
- TypeORM: update entity file
- Others: according to ORM convention
- Prisma: update
-
Generate migration file
- Prisma:
npx prisma migrate dev --name {{input.description | slugify}} - Drizzle:
npx drizzle-kit generate - Knex:
npx knex migrate:make {{input.description | slugify}} - Manual: create timestamped migration file
- Prisma:
-
Update seed data (if applicable)
- Add/update seed for new/changed tables
- Ensure seed is idempotent
-
Update types (if generated)
- Prisma:
npx prisma generate - Drizzle: types auto-generated from schema
- Prisma:
-
Test migration
- Run migration on test database
- Verify schema is correct
- Run existing tests (ensure nothing breaks)
Script
#!/bin/bash
# Detect ORM
if [ -f "prisma/schema.prisma" ]; then
echo "ORM: Prisma"
echo "Run: npx prisma migrate dev"
elif [ -f "drizzle.config.ts" ] || [ -f "drizzle.config.js" ]; then
echo "ORM: Drizzle"
echo "Run: npx drizzle-kit generate"
elif [ -f "knexfile.js" ] || [ -f "knexfile.ts" ]; then
echo "ORM: Knex"
echo "Run: npx knex migrate:make"
elif ls src/entities/*.ts 1>/dev/null 2>&1; then
echo "ORM: TypeORM"
fi
Validation
- Schema/model updated correctly
- Migration file generated
- Migration runs successfully (up)
- Migration rollback works (down)
- Existing tests still pass
- Types updated (if applicable)
- Seed data updated (if applicable)
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.
- 7d ago First seen · 86 lines · 12 tokens per session scan A 88fe730524b6
migration is a skill published in the GitHub repository porcupine-md/jonggrang (11 stars, last pushed 10d ago), licensed MIT. It adds 12 tokens to every session and 667 once invoked, about $0.0001 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-30.
Other skills, from other repositories
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.