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 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/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/random6913/claude-code-superkit/db-patterns"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/db-patterns.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.00022 | $0.01263 |
| Opus 5.5 | $0.00009 | $0.00505 |
| Sonnet 5.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 1mo 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 — 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.
- 1mo ago 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 (3 stars, last pushed 14d ago), licensed MIT. It adds 22 tokens to every session and 1,263 once invoked, about $0.0001 per session on Opus 5.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-patterns
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Quick reference for common patterns, index types, data types, and anti-pattern detection. Based on Supabase best practices.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
memstack-security-rls-guardian
Use this skill when creating or altering database tables in Supabase or PostgreSQL projects. Triggers include: CREATE TABLE, ALTER TABLE, migration files, 'RLS', 'row level security', 'new table', 'database schema'. Enforces Row Level Security policies on every table to prevent unauthorized data access. Do NOT use for…
database-patterns
DB schema design and query tuning: normalization, indexing, N+1, transactions, EXPLAIN. Triggers: schema, index, slow query, N+1, PostgreSQL, MySQL, EXPLAIN, deadlock, query plan.
kysely
Guidelines for developing with Kysely, a type-safe TypeScript SQL query builder with autocompletion support.
postgresql-best-practices
PostgreSQL development best practices for schema design, query optimization, and database administration.