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 Yaomeng1749/claude-code-digital-nomad-config-pack --skill database-migrationsgit clone --depth 1 https://github.com/Yaomeng1749/claude-code-digital-nomad-config-packWrote 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/yaomeng1749/claude-code-digital-nomad-config-pack/database-migrations)<a href="https://agentmods.dev/skills/yaomeng1749/claude-code-digital-nomad-config-pack/database-migrations"><img src="https://agentmods.dev/badge/skills/yaomeng1749/claude-code-digital-nomad-config-pack/database-migrations.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.00061 | $0.02206 |
| Opus 5 | $0.00030 | $0.01103 |
| Sonnet 5 | $0.00012 | $0.00441 |
| Haiku 4.5 | $0.00006 | $0.00221 |
Grade A, and why
database-migrations 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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 349 lines · 61 tokens per session scan A 1f02085fdd98
database-migrations is a skill published in the GitHub repository Yaomeng1749/claude-code-digital-nomad-config-pack (4 stars, last pushed 4mo ago), with no licence file. It adds 61 tokens to every session and 2,206 once invoked, about $0.0003 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-03.
Other skills, from other repositories
data-dictionary
Gerar dicionario de dados a partir de schema (Drizzle, Prisma, SQL, TypeScript types). Documenta tabelas, colunas, tipos, relacoes, constraints. Trigger quando usuario quer documentar banco de dados ou schema.
ag-referencia-supabase
Patterns para Supabase, PostgreSQL, RLS, migrations, e Zod schemas.
ag-migrar-dados
Gera e valida migration files para mudancas de schema de banco de dados. Detecta ORM do projeto e gera migrations no formato nativo.
ag-incorporar-modulo
Executa incorporacao de um modulo seguindo o roadmap e taskplan. Implementa ACL, migrations, sync, UI adapters. Um modulo por vez.
ag-referencia-seguranca-rules
Regras inegociaveis de seguranca: RLS, audit trail, LGPD, mascaramento PII, niveis de permissao. Reference skill carregado on-demand.
supabase-postgres-best-practices
Use when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations — including indexing, connection pooling, RLS policies, and locking. Postgres performance best practices from Supabase.