drizzle-best-practices: Instructions file for Codex

AGENTS.md

drizzle-best-practices AGENTS.md is an instructions file for Codex, OpenCode from honra-io/drizzle-best-practices. It costs 817 tokens per session, scanned A, original, MIT.

A best-practices guide for Drizzle ORM with PostgreSQL. Drizzle is a TypeScript library for defining database schemas and queries, while PostgreSQL is a relational database.

In plain words
What is it for?
Use it when designing PostgreSQL schemas, writing Drizzle queries, defining relationships, configuring migrations, or reviewing database performance and serverless setup.
Why use it?
It provides project rules and topic-specific references for database design, queries, relations, migrations, types, performance, drivers, and advanced SQL use.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

This is honra-io/drizzle-best-practices's own configuration. It tells Codex and OpenCode how to work on drizzle-best-practices itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything drizzle-best-practices configures →

Reuse

Borrowing it

Nothing to install: this file belongs to honra-io/drizzle-best-practices. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/honra-io/drizzle-best-practices/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/honra-io/drizzle-best-practices

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for drizzle-best-practices AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/honra-io/drizzle-best-practices/agents-md/github.svg)](https://agentmods.dev/instructions/honra-io/drizzle-best-practices/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/honra-io/drizzle-best-practices/agents-md"><img src="https://agentmods.dev/badge/instructions/honra-io/drizzle-best-practices/agents-md/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.

agentmods 80×15 button for drizzle-best-practices AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/honra-io/drizzle-best-practices/agents-md"><img src="https://agentmods.dev/badge/instructions/honra-io/drizzle-best-practices/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 817 This file is loaded in full into every session.
When invoked 817 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00817 $0.00817
Opus 5 $0.00409 $0.00409
Sonnet 5 $0.00163 $0.00163
Haiku 4.5 $0.00082 $0.00082

Measured 8d ago against content hash 30cbb0f60a2e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

drizzle-best-practices AGENTS.md 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 8d 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.

AGENTS.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Drizzle ORM Best Practices (PostgreSQL)

Structure

drizzle-best-practices/
  SKILL.md                # Main skill file - read this first
  AGENTS.md               # This navigation guide
  CLAUDE.md               # Symlink to AGENTS.md
  references/
    engine-postgres.md    # Postgres-specific types, features, and idioms
    schema-*.md           # Schema design patterns
    query-*.md            # Query patterns
    relations-*.md        # Relation definitions and relational queries
    migrations-*.md       # Drizzle Kit configuration and workflow
    types-*.md            # TypeScript type inference and custom types
    perf-*.md             # Performance optimization
    driver-*.md           # Driver setup and serverless configuration
    advanced-*.md         # Dynamic queries, raw SQL, power-user patterns
    _sections.md          # Full index of all reference files

Usage

  1. Read SKILL.md for the main skill instructions
  2. Browse references/ for detailed documentation on specific topics
  3. Reference files are loaded on-demand — read only what you need

Comprehensive best practices guide for Drizzle ORM with PostgreSQL. Contains guidance across 8 categories, prioritized by impact to help AI agents generate correct, performant, and idiomatic Drizzle code.

When to Apply

Reference these guidelines when:

  • Defining table schemas with pgTable
  • Writing select, insert, update, or delete queries
  • Setting up relations between tables
  • Configuring drizzle-kit for migrations
  • Inferring TypeScript types from your schema
  • Choosing between the SQL-like API and the relational query API
  • Optimizing query performance
  • Integrating Drizzle with serverless Postgres providers (Neon, Supabase, etc.)

Rule Categories by Priority

Priority Category Impact Prefix
1 Schema Design CRITICAL schema-
2 Query Patterns CRITICAL query-
3 Relations HIGH relations-
4 Migrations HIGH migrations-
5 Type Safety MEDIUM-HIGH types-
6 Performance MEDIUM perf-
7 Database Drivers MEDIUM driver-
8 Advanced Patterns LOW advanced-

Read the full file on GitHub · 103 lines

Changes

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.

  1. 8d ago First seen · 103 lines · 817 tokens per session scan A 30cbb0f60a2e

Subscribe to this mod's changes

drizzle-best-practices AGENTS.md is an instructions file published in the GitHub repository honra-io/drizzle-best-practices (19 stars, last pushed 3mo ago), licensed MIT. It adds 817 tokens to every session, about $0.0041 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.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens