Borrowing it
Nothing to install: this file belongs to PackmindHub/skillsight. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PackmindHub/skillsight/main/.claude/commands/create-drizzle-repository.mdgit clone --depth 1 https://github.com/PackmindHub/skillsightWrote 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/commands/packmindhub/skillsight/create-drizzle-repository)<a href="https://agentmods.dev/commands/packmindhub/skillsight/create-drizzle-repository"><img src="https://agentmods.dev/badge/commands/packmindhub/skillsight/create-drizzle-repository.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.1 | $0.00051 | $0.00534 |
| Opus 5 | $0.00026 | $0.00267 |
| Sonnet 5 | $0.00010 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
create-drizzle-repository 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 7d 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
Create a Drizzle Repository
Scaffold a new data-access repository the way every existing one is built: a port interface in domain/ports/, a Drizzle*Repository implementation in infrastructure/repositories/, and DI wiring in bootstrap/compose.ts. Use this when a use case needs to read or write a new table.
When to Use
- A new use case needs persistence for an entity that has no repository yet.
- You added a table to
backend/src/db/schema.tsand need typed access to it. - Splitting an over-broad repository into a focused one.
Checkpoints
- What is the entity/aggregate name (drives
I<Name>RepositoryandDrizzle<Name>Repository)? - Does the table already exist in
backend/src/db/schema.ts, or is a migration needed first? - Which read/write methods does the consuming use case actually require?
Steps
1. Declare the port
Add backend/src/domain/ports/<name>-repository.ts with an interface I<Name>Repository. Methods return domain entities (from domain/), use Promise<Entity | null> for single lookups, and never reference Drizzle row types.
2. Implement with Drizzle
Add backend/src/infrastructure/repositories/drizzle-<name>-repository.ts: export class Drizzle<Name>Repository implements I<Name>Repository with constructor(private readonly db: AppDb) {}. Use the Drizzle query builder; return row ?? null for single rows. For "IN (list)" filters use inArray(column, jsArray) from drizzle-orm — never ANY(${arr}::text[]).
3. Wire into the DI container
Instantiate the repository in backend/src/bootstrap/compose.ts and expose it so route handlers can inject it into use cases.
4. Migrate if the schema changed
If you touched backend/src/db/schema.ts, run bun run migrate:generate from backend/ (never hand-author migration files), then bun run migrate:run.
5. Verify
Run bun run typecheck and bun run lint; add a use-case test that supplies a stubbed I<Name>Repository.
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.
- 7d ago First seen · 42 lines · 51 tokens per session scan A c4fe96c4d83e
create-drizzle-repository is a command published in the GitHub repository PackmindHub/skillsight (9 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 51 tokens to every session and 534 once invoked, about $0.0003 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
crud
Generates a complete CRUD domain in the house pattern (NestJS or Express + Prisma — picked by the project's real stack, multi-tenant).
brainstorm
Pre-implementation collaborative requirement exploration and design (conversational brainstorm).
ccc-multi-backend
Backend-focused multi-model workflow: Research → Plan → Execute → Review, Codex-led.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.