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/random6913/claude-code-superkit/db-patternsnpx skills add RaNDoM6913/claude-code-superkit --skill db-patternsgit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/db-patterns)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/db-patterns"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/db-patterns.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 | $0.00022 | $0.01263 |
| Opus 5 | $0.00011 | $0.00632 |
| Sonnet 5 | $0.00004 | $0.00253 |
| Haiku 4.5 | $0.00002 | $0.00126 |
Grade A, and why
db-patterns 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 yesterday.
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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Patterns
Current State
- Latest migration: !
ls backend/migrations/*.up.sql | sort | tail -1 | xargs basename - Total migrations: !
ls backend/migrations/*.up.sql 2>/dev/null | wc -l | tr -d ' ' - Repository count: !
ls backend/internal/repo/postgres/*_repo.go 2>/dev/null | wc -l | tr -d ' '
Stack
- PostgreSQL 16
- Driver:
jackc/pgx/v5(connection pool viapgxpool) - No ORM — raw SQL queries
Repository Pattern
type UserRepo struct {
pool *pgxpool.Pool
}
func NewUserRepo(pool *pgxpool.Pool) *UserRepo {
return &UserRepo{pool: pool}
}
// Nil-safety check
func (r *UserRepo) Ready() bool {
return r != nil && r.pool != nil
}
Common Query Patterns
SELECT single row
func (r *UserRepo) GetByID(ctx context.Context, id int64) (*domain.User, error) {
var u domain.User
err := r.pool.QueryRow(ctx, `
SELECT id, name, email, created_at
FROM users
WHERE id = $1
`, id).Scan(&u.ID, &u.Name, &u.Email, &u.CreatedAt)
if err != nil {
if errors.Is(err, pgx.ErrNoRows) {
return nil, nil // or return specific ErrNotFound
}
return nil, fmt.Errorf("UserRepo.GetByID: %w", err)
}
return &u, nil
}
SELECT multiple rows
func (r *UserRepo) List(ctx context.Context, limit, offset int) ([]domain.User, error) {
rows, err := r.pool.Query(ctx, `
SELECT id, name, email, created_at
FROM users
ORDER BY created_at DESC
LIMIT $1 OFFSET $2
`, limit, offset)
if err != nil {
return nil, fmt.Errorf("UserRepo.List: %w", err)
}
defer rows.Close()
var users []domain.User
for rows.Next() {
var u domain.User
if err := rows.Scan(&u.ID, &u.Name, &u.Email, &u.CreatedAt); err != nil {
return nil, fmt.Errorf("UserRepo.List scan: %w", err)
}
users = append(users, u)
}
return users, rows.Err()
}
INSERT
func (r *UserRepo) Create(ctx context.Context, u *domain.User) error {
_, err := r.pool.Exec(ctx, `
INSERT INTO users (name, email, created_at)
VALUES ($1, $2, now())
`, u.Name, u.Email)
if err != nil {
return fmt.Errorf("UserRepo.Create: %w", err)
}
return nil
}
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.
- yesterday First seen · 184 lines · 22 tokens per session scan A 74c56b477bea
db-patterns is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,263 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-03.
Other skills, from other repositories
postgres
Use when designing, querying, or managing a PostgreSQL database. Enforces enterprise production rules for advanced querying, composite indexing, JSONB data handling, and strict optimization patterns (avoiding N+1). Keywords: PostgreSQL query, JSONB, pg, pgvector, RLS, Postgres migration. MUST-ASK: Require explicit…
qlocalclonedb
Clone a staging tenant's database into a named local Postgres DB for realistic local testing — copies schema + data so you can reproduce issues against production-shaped data. Use before local E2E when you need real tenant data; qspinuplocal calls it when a project ships a local-DB bootstrap.
qspinuplocal
Spin up your primary service locally against a local Postgres DB for testing — env wiring, optional migrations, health check. Single-service by design; adapt the start command to your stack.
migration-preview
Use when reviewing or writing a database migration, schema change, or data backfill — anything that alters durable data shape.
Supabase Expert
Database and backend knowledge for business operators — table design, auth setup, row-level security, storage, and edge functions explained in plain English. Not a developer guide — domain expertise for building your backend on Supabase.
alloydb-basics
Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB model context protocol (MCP) tools for automated database operations.