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 hiromaily/go-crypto-wallet --skill db-migrationgit clone --depth 1 https://github.com/hiromaily/go-crypto-walletWrote 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/hiromaily/go-crypto-wallet/db-migration)<a href="https://agentmods.dev/skills/hiromaily/go-crypto-wallet/db-migration"><img src="https://agentmods.dev/badge/skills/hiromaily/go-crypto-wallet/db-migration/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/hiromaily/go-crypto-wallet/db-migration"><img src="https://agentmods.dev/badge/skills/hiromaily/go-crypto-wallet/db-migration.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.00029 | $0.00662 |
| Opus 5 | $0.00015 | $0.00331 |
| Sonnet 5 | $0.00006 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
db-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 9d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Migration Workflow
Workflow for database schema and migration changes.
Prerequisites
- Use
git-workflowSkill for branch, commit, and PR workflow. - Refer to
.claude/rules/hcl.mdfor HCL schema rules (SSOT). - Refer to
.claude/rules/sql.mdfor SQL query rules (SSOT).
Applicable Files
| Path | Description |
|---|---|
tools/atlas/schemas/{db_dialect}/*.hcl |
HCL schema definitions (source of truth) |
tools/sqlc/queries/{db_dialect}/*.sql |
SQLC query definitions |
Workflow
1. Modify Schema (HCL)
Edit HCL files in tools/atlas/schemas/{db_dialect}/.
Dialect directories:
tools/atlas/schemas/postgres/*.hcltools/atlas/schemas/mysql/*.hcl
2. Verify HCL (from rules/hcl.md)
make atlas-fmt && make atlas-lint
3. Regenerate All Artifacts
Run all three targets after modifying HCL schemas:
# Regenerate migrations, extract SQLC schemas, and generate Go code for PostgreSQL
make regenerate-all-from-atlas
# Regenerate for MySQL
make regenerate-all-from-atlas-mysql
# Convert PostgreSQL schemas to SQLite and generate Go code for SQLite
make regenerate-all-from-atlas-sqlite
Each target handles: Atlas migrations → Docker DB reset → SQLC schema extraction → SQLC code generation.
4. Verify Migration Files
After running the regenerate targets, confirm each DB dialect has exactly one migration SQL file:
tools/atlas/migrations/postgres/{db-name}/*.sql← one file, updatedtools/atlas/migrations/mysql/{db-name}/*.sql← one file, updated
DB names: keygen, sign, watch
5. Verify Go Code
make check-build && make go-test
Self-Review Checklist
- HCL format/lint passes
-
make regenerate-all-from-atlassucceeds (postgres) -
make regenerate-all-from-atlas-mysqlsucceeds (mysql) -
make regenerate-all-from-atlas-sqlitesucceeds (sqlite) - Each
tools/atlas/migrations/{postgres,mysql}/{db-name}/has exactly one.sqlfile and it is updated - SQLC generates correctly
- Go build passes
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.
- 9d ago First seen · 88 lines · 29 tokens per session scan A da2a07f7d907
db-migration is a skill published in the GitHub repository hiromaily/go-crypto-wallet (127 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 662 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-09-01.
Other skills, from other repositories
db-branching
Branches Neon, Turso, or Supabase per git worktree for isolated schema work. Use when a worktree changes the schema, or on mention of Neon, Turso, Prisma.
agent-wallet
Operate a non-custodial blockchain wallet on-chain (EVM and Bitcoin), no exchange or MetaMask. Create or import a wallet, balances, send native/ERC-20/BTC, swap tokens, compile/deploy/call Solidity. Trigger on wallet, crypto, ETH, BTC, ERC-20, token, send, transfer, swap, trade, Solidity, contract, on-chain, testnet…
agent-solidity
Write, audit and deploy Solidity smart contracts through a gated multi-step workflow (spec, threat model, design, implementation, in-process EVM proof, security audit, deployment), with a local EVM sandbox that needs no Foundry, Hardhat, anvil, node or funds. Trigger on Solidity, smart contract, .sol, ERC-20, ERC-721…
PostgreSQL
PostgreSQL 17.x — data types, DDL, DML, queries, indexes, full text search, concurrency, performance, functions.
pqc-scan
Inventory the cryptography in a codebase that a quantum computer would break, and report what the scan could not read. Use when asked about post-quantum readiness, cryptographic inventory, a CBOM, or which algorithms a project signs with.
database-migration-assistant
PostgreSQL migration assistant that plans, applies, and rolls back schema changes with drift detection for safe AI-agent execution.