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 agentmods add skills/dongduong2001/pudo-code-system/databasenpx skills add DongDuong2001/pudo-code-system --skill databasegit clone --depth 1 https://github.com/DongDuong2001/pudo-code-systemWhat 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 | $0.00012 | $0.00165 |
| Opus 5 | $0.00006 | $0.00082 |
| Sonnet 5 | $0.00002 | $0.00033 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
database-plan 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 2d 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.
What it actually says
Database Planning Skill
This skill is essential when designing data storage solutions and defining schema boundaries.
When to use this skill
- When determining whether to use SQL vs NoSQL vs Time-Series databases.
- When designing entity-relationship diagrams (ERD) schemas.
- When planning indexing, partitioning, or sharding strategies.
Guidelines
- Normalize data by default to reduce redundancy, but denormalize strategically for read-heavy performance bottlenecks.
- Plan indexes based on expected query patterns, not just foreign keys. Remember that excessive indexing slows down write operations.
- Avoid using UUIDs/GUIDs as primary clustered keys in massive tables where sequential inserts are critical for performance, unless mitigated by the DB engine.
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.
- 2d ago First seen · 19 lines · 12 tokens per session scan A dda80145a861
database-plan is a skill published in the GitHub repository DongDuong2001/pudo-code-system (5 stars, last pushed 26d ago), licensed MIT. It adds 12 tokens to every session and 165 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-31.
Other skills, from other repositories
model-domain
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates specs/tech-architecture/tech-stack.md and specs/adr/ inline as decisions crystallise. Use when user wants to stress-test a plan against their project's domain language and documented decisions.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
modeling-warehouse-foundations
Shared foundations for building reusable data models in PostHog, on either of two stacks: PostHog-native data-warehouse views / materialized views (HogQL, via the view- MCP tools), or an external dbt project (sources.yml + staging/marts + schema tests) run against your own or PostHog's managed warehouse. Read before…
modeling-dimension-tables
Build reusable dimension / lookup tables for a star schema — country/region, timezone, currency, date, plan/product, and other descriptive attributes — on either PostHog data-warehouse views (HogQL) or an external dbt project. Use when the user wants to model dimension tables, lookup tables, a star schema, conformed…
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.