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 monkilabs/opencastle --skill drizzle-ormgit clone --depth 1 https://github.com/monkilabs/opencastleWrote 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/monkilabs/opencastle/drizzle-orm)<a href="https://agentmods.dev/skills/monkilabs/opencastle/drizzle-orm"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/drizzle-orm/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/monkilabs/opencastle/drizzle-orm"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/drizzle-orm.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.00048 | $0.00492 |
| Opus 5.5 | $0.00019 | $0.00197 |
| Sonnet 5.5 | $0.00010 | $0.00098 |
| Haiku 4.5 | $0.00005 | $0.00049 |
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 11d 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
Drizzle ORM
Gotchas
drizzle(client, { schema })— omit{ schema }and thedb.query.*relational API silently does not exist.relations()is ORM-level metadata only and creates no constraint. Definereferences(() => users.id, { onDelete: 'cascade' })as well; you need both.- Types come from
typeof table.$inferSelect/$inferInsert— never hand-write them. - SQL-like API (
db.select().from()) for joins and aggregates; relational API (db.query.x.findMany({ with: {...} })) for nested reads.insert/update/deletegive back nothing usable without.returning(). - Inside
db.transaction(async (tx) => ...)every call must usetx; a straydbcall runs outside the transaction. - Prepared statements need
sql.placeholder('id')+.prepare('name'), then.execute({ id }). - Partial selects (
db.select({ id: users.id })) avoid loading unused columns; declare indexes in the table definition.
drizzle-kit
generate→ review the SQL in theoutdir →migrate.pushis dev-only. Never edit generated SQL; fix the schema and regenerate.checkvalidates migration history consistency.- A column rename generates DROP + ADD, i.e. data loss. Hand-write the migration file instead —
ALTER TABLE users RENAME COLUMN old_name TO new_name;— thenmigrateapplies it. - A new non-nullable column takes two migrations: add nullable → backfill → add
.notNull()→ migrate again. - The programmatic migrator needs a single connection:
postgres(url, { max: 1 }), thenmigrate(drizzle(client), { migrationsFolder: './drizzle' }), then close it. drizzle.config.tsmust supplydialect,schema,out, anddbCredentials.urlbefore any command runs.
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.
- 11d ago Changed · -21 tokens per session ba6a25840570
- 12d ago First seen · 27 lines · 69 tokens per session scan A 7a7e37481dab
drizzle-orm is a skill published in the GitHub repository monkilabs/opencastle (80 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 492 once invoked, about $0.0002 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-10-04.
Other skills, from other repositories
transactional-patterns
Use when defining or debugging Spring Boot 3 database transaction boundaries, rollback, propagation, optimistic-lock retries, or commit-bound events. For duplicate HTTP commands use idempotency-patterns; for reactive transactions use webflux-reactive-patterns.
spring-data-jpa
Use when generating JPA entities, repositories, queries, or anything touching the persistence layer. Covers entity conventions, N+1 prevention, projections, and query patterns.
spring-data-redis
Use when implementing caching, session storage, rate limiting, or any Redis integration. Covers cache-aside pattern, key naming, TTL strategy, and serialization config.
flyway-migrations
Use when creating database migrations, schema changes, seed data, or any SQL that modifies database structure. Covers Flyway naming conventions, versioning, and safe migration patterns.
idempotency-patterns
Use when making retried HTTP commands or message processing safe against duplicate effects, including database-backed request keys, payload conflicts and concurrent retries. Do not apply caching as a substitute for business idempotency.
multi-tenancy
Use when implementing tenant resolution, database or schema isolation, tenant-aware JPA, reactive tenant context, migrations, caching, jobs, or authorization in Spring Boot 3.