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 andreapollastri/larapilot --skill larapilot-db-upgradegit clone --depth 1 https://github.com/andreapollastri/larapilotWrote 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/andreapollastri/larapilot/larapilot-db-upgrade)<a href="https://agentmods.dev/skills/andreapollastri/larapilot/larapilot-db-upgrade"><img src="https://agentmods.dev/badge/skills/andreapollastri/larapilot/larapilot-db-upgrade/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/skills/andreapollastri/larapilot/larapilot-db-upgrade"><img src="https://agentmods.dev/badge/skills/andreapollastri/larapilot/larapilot-db-upgrade.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.00116 | $0.01896 |
| Opus 5.5 | $0.00046 | $0.00758 |
| Sonnet 5.5 | $0.00023 | $0.00379 |
| Haiku 4.5 | $0.00012 | $0.00190 |
Grade A, and why
larapilot-db-upgrade 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 15d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Larapilot — Database Upgrade
You move the project to a new version of its database engine, or to another engine. You check first and report every criticality; then — when the user says so — you make the code and the configuration portable to the target, prove it on a local rehearsal with the test suite, and write the runbook that moves the data and switches production. You never touch a production database or server.
Context
php artisan larapilot:context db-upgrade — with --session={token} when this conversation already holds one, --fresh after a compaction. Read every file under data.runtime.read, none under loaded; read an on_demand file when its when comes true. Settings, paths, and data.project come from that envelope: no config-show.
Output Economy
Moderate — the readiness verdict, the criticalities, and the checklist as tables; during the run, one line per step. Findings with file and line go in the reports.
The Team (this phase)
| Agent | Role |
|---|---|
| 🤖 Zoey | AI Guru — output economy, session/credit risk (every skill) |
| 🗄️ Mike | Database Expert — the transition, the SQL, types, collations, users |
| 🔄 Sabrine | Legacy Porting & Migration Specialist — moving the data, verification, cutover |
| 🔧 Alex | Full-Stack Developer — raw SQL to the query builder, migrations, config |
| 🧪 Anne | Test Architect — the suite on the target engine |
| 🚀 Jack | DevOps Engineer — compose services, CI containers, managed databases, the runbook |
Config & CLI
php artisan larapilot:stack --only=database,pins— engine, server version, connections, imagesphp artisan larapilot:upgrade-check --db={engine}:{version} --report— scan of the code, pins, checklist, criticalities;--db-from={engine}:{version}when the server does not answer- Boost
Database Schema— tables, column types, indexes, foreign keys of the database of today php artisan larapilot:spec-add --file=— backlog mode onlyphp artisan larapilot:decision-log— when the journal is on
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.
- 15d ago First seen · 109 lines · 116 tokens per session scan A 321216cad721
larapilot-db-upgrade is a skill published in the GitHub repository andreapollastri/larapilot (22 stars, last pushed yesterday), licensed MIT. It adds 116 tokens to every session and 1,896 once invoked, about $0.0005 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-10-02.
Other skills, from other repositories
flyway-or-liquibase-detection
Auto-detect the project's DB migration tool and follow its conventions. Never use both. Use when designing or writing a schema change.
db-context-supabase
Validate that a Supabase MCP server is reachable, introspect a subset of the database (tables, columns, RLS policies), and persist it as DBCONTEXT.md. Read-only, never destructive SQL. Falls back to the local Supabase CLI when no MCP server is reachable. Use when the task touches Supabase data, schema or RLS and…
db-context-postgres
Validate that a non-Supabase Postgres database (Cloud SQL, RDS, self-hosted) is reachable, introspect a scoped subset of its schema, and persist it as DBCONTEXT.md. Read-only, opt-in. Use when work touches that database and planning needs verified schema, or DBCONTEXT.md is stale. Do not use without a task (run…
mysql-patterns
Use when designing MySQL schema features or applying advanced MySQL patterns in Laravel — upserts, JSON columns, full-text search, partitioning, replication/read-write splitting, and deadlock handling — beyond the query tuning already in the SQL rules.
postgres-patterns
Use when designing PostgreSQL schema features or applying advanced Postgres patterns in Laravel — GIN/BRIN/partial/covering indexes, jsonb, ON CONFLICT upserts, SKIP LOCKED queue workers, cursor pagination, RLS, and timestamptz/numeric typing — beyond the query tuning already in the SQL rules.
redis-patterns
Use when using Redis in a Laravel app — caching strategies, atomic/distributed locks, rate limiting, stampede protection, pub/sub, pipelines, and key/TTL design beyond raw query tuning.