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 commands/srstomp/pokayokay/dbgit clone --depth 1 https://github.com/srstomp/pokayokayWhat 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.00005 | $0.00458 |
| Opus 5 | $0.00003 | $0.00229 |
| Sonnet 5 | $0.00001 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
db 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 Design Workflow
Design or review database for: $ARGUMENTS
Steps
1. Identify Database Context
Detect from project:
- ORM: Prisma, Drizzle, TypeORM, Sequelize
- Database: PostgreSQL, MySQL, SQLite, MongoDB
- Existing schema: Check for migration files
2. Identify Task Type
From $ARGUMENTS, determine the goal:
- Schema design: New tables, relationships, constraints
- Migration: Plan safe schema changes
- Optimization: Index design, query analysis
- Review: Audit for anti-patterns
3. Execute Task
For Schema Design:
- Identify entities and relationships
- Define constraints (PK, FK, unique, check)
- Plan indexes for query patterns
- Consider normalization level
For Migrations:
- Plan backward-compatible changes
- Design rollback strategy
- Handle data migrations
- Test on staging first
For Optimization:
- Analyze slow queries with EXPLAIN
- Recommend indexes
- Identify N+1 patterns
- Suggest denormalization if needed
4. Generate Artifacts
- Schema diagram (Mermaid ERD)
- Migration files (Prisma/Drizzle format)
- Index recommendations
- Query improvements
5. Create Implementation Tasks
npx @stevestomp/ohno-cli create "DB: [specific change]" -t feature
Covers
- Entity relationship modeling
- Index strategy
- Migration planning
- Query optimization
- Constraint design
- Data integrity
Related Commands
/pokayokay:api- Design API for database entities/pokayokay:work- Implement schema changes/pokayokay:test- Database testing strategy
Skill Integration
When database work involves:
- API changes → Also load
api-designskill - Data security → Also load
security-auditskill - Query monitoring → Also load
observabilityskill
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 · 77 lines · 5 tokens per session scan A d0f53ff0820c
db is a command published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 458 once invoked, about $0.0000 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 commands, from other repositories
bucket-advance
Advances a cursor to fetch or process the next batch of documents.
schema
Interactive schema design — delegates to schema-designer agent.
d1-migration
Run D1 migration workflow — generate, inspect, apply.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
ads_dataset-audit-generate
Inventory warehouse tables, identify duplicates, grade governance maturity.
symfony-migrations
Create and manage Doctrine migrations for database schema changes.