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/recca0120/code-quest/drizzle-ormnpx skills add recca0120/code-quest --skill drizzle-ormgit clone --depth 1 https://github.com/recca0120/code-questWhat 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.00047 | $0.00789 |
| Opus 5 | $0.00023 | $0.00394 |
| Sonnet 5 | $0.00009 | $0.00158 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
drizzle-orm 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drizzle ORM
File Structure
apps/server/
├── src/db/
│ ├── schema-sqlite.ts # sqliteTable() definitions
│ ├── schema-mysql.ts # mysqlTable() definitions
│ ├── schema-columns.ts # Shared column name constants
│ ├── sqlite-client.ts # drizzle(better-sqlite3) factory
│ └── mysql-client.ts # drizzle(mysql2) factory
├── src/services/
│ ├── drizzle-session-store.ts # Session CRUD
│ ├── drizzle-raw-store.ts # Raw event append/query
│ ├── composite-raw-store.ts # Multi-backend wrapper
│ └── composite-session-store.ts
├── src/scripts/
│ ├── migrate-sqlite.ts
│ └── migrate-mysql.ts
├── drizzle-sqlite.config.ts
├── drizzle-mysql.config.ts
└── drizzle/
├── sqlite/ # 10 migration files
└── mysql/ # 10 migration files
Schema Pattern
Both dialects share column names via schema-columns.ts:
// schema-columns.ts
export const SESSION_COLUMNS = { id, provider, command, args, cwd, mode, role, parentId, sessionId, title, status, createdAt };
export const RAW_ENTRY_COLUMNS = { id, sessionId, promptId, dir, raw, seq, createdAt };
Schema consistency is verified by src/__tests__/schema-consistency.test.ts using getTableColumns().
Connection Setup
SQLite (sqlite-client.ts): drizzle(new Database(path), { schema }) — WAL mode + foreign keys enabled.
MySQL (mysql-client.ts): drizzle(mysql.createPool(url), { schema, mode: 'default' }).
Query Patterns
// Select with pagination
db.select().from(sessions).where(ne(sessions.status, 'deleted')).orderBy(desc(sessions.createdAt)).limit(limit).offset(offset)
// Insert
db.insert(rawEntries).values({ sessionId, raw, seq, createdAt })
// Update
db.update(sessions).set({ title }).where(eq(sessions.id, id))
// Delete
db.delete(sessions).where(eq(sessions.id, id))
// Count
db.select({ count: count() }).from(sessions)
Operators: eq(), ne(), desc(), asc(), count().
Migration Workflow
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 · 101 lines · 47 tokens per session scan A bbc9e2099789
drizzle-orm is a skill published in the GitHub repository recca0120/code-quest (11 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 789 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…