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 rtazima/claude-proj-blueprint --skill migrationgit clone --depth 1 https://github.com/rtazima/claude-proj-blueprintWrote 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/rtazima/claude-proj-blueprint/migration)<a href="https://agentmods.dev/skills/rtazima/claude-proj-blueprint/migration"><img src="https://agentmods.dev/badge/skills/rtazima/claude-proj-blueprint/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.00047 | $0.00983 |
| Opus 5 | $0.00023 | $0.00491 |
| Sonnet 5 | $0.00009 | $0.00197 |
| Haiku 4.5 | $0.00005 | $0.00098 |
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration
Guide safe database schema changes: assess impact, generate up+down migration, verify reversibility, and create ADR for destructive changes.
Rules
- Every schema change is a migration — never alter the DB manually
- Up AND down — every migration must be reversible (unless explicitly documented why not)
- Zero-downtime by default — no changes that lock tables or break running queries
- ADR for destructive changes — DROP, column type change, or data loss requires an ADR
- Test the migration — run up, verify, run down, verify, run up again
- One concern per migration — don't mix schema changes with data migrations
- Follow naming convention —
[SPEC](e.g.,YYYYMMDDHHMMSS_description.sql)
Risk Assessment
Before creating any migration, classify the risk:
| Risk | Examples | Required |
|---|---|---|
| 🟢 Low | Add nullable column, add index, create table | Migration + tests |
| 🟡 Medium | Add NOT NULL column with default, rename column, add constraint | Migration + tests + team review |
| 🔴 High | Drop column/table, change column type, data migration | Migration + tests + ADR + rollback plan |
Workflow
Phase 1: Assess
- Read the PRD/requirement that drives the schema change
- Check
docs/specs/versioning/for migration naming and strategy - Check
docs/specs/data-architecture/for modeling conventions - List ALL changes needed (don't discover them mid-migration)
- Classify risk level (🟢/🟡/🔴) for each change
Phase 2: Design
For each change, document:
Change: [what is changing]
Risk: [🟢/🟡/🔴]
Up: [SQL or ORM operation]
Down: [reverse operation]
Zero-downtime: [yes/no — if no, explain why and what the plan is]
Data impact: [rows affected estimate, if relevant]
Phase 3: Generate
- Create migration file following naming convention:
[SPEC] - Write the up migration
- Write the down migration (rollback)
- If data migration is needed, separate it from schema migration
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 · 101 lines · 47 tokens per session scan A 2b9be881c778
migration is a skill published in the GitHub repository rtazima/claude-proj-blueprint (20 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 983 once invoked, about $0.0002 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
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
init-workspace-documentation
Skill "init-workspace-documentation" from griddynamics/rosetta, covering agent memory.md, agent memory, preventive rules, what worked and what failed.
solr-schema
To design and audit Solr schemas: field types, analyzers, docValues, solrconfig.
architecture-paradigm-space-based
Applies data-grid architecture for high-traffic stateful workloads. Use when a single database cannot scale and in-memory partitioning is needed.
cmdb-patterns
Create ServiceNow CIs and cmdbrelci relationships, walk upstream/downstream impact, detect orphan/stale CIs, and align discovered CIs with the proper sysclassname hierarchy.
firebase-security-expert
Firebase security expert to audit Security Rules (Firestore/Realtime Database/Storage), authentication, API keys, data leakage prevention, and App Check configuration / Ahli keamanan Firebase untuk audit Security Rules (Firestore/Realtime Database/Storage), autentikasi, API keys, pencegahan kebocoran data, dan…