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/cohen-liel/hivemind/prisma-ormnpx skills add cohen-liel/hivemind --skill prisma-ormgit clone --depth 1 https://github.com/cohen-liel/hivemindWrote 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/cohen-liel/hivemind/prisma-orm)<a href="https://agentmods.dev/skills/cohen-liel/hivemind/prisma-orm"><img src="https://agentmods.dev/badge/skills/cohen-liel/hivemind/prisma-orm.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 | $0.00045 | $0.01189 |
| Opus 5 | $0.00023 | $0.00594 |
| Sonnet 5 | $0.00009 | $0.00238 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade A, and why
prisma-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 4d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prisma ORM Patterns
Schema Design
// prisma/schema.prisma
generator client {
provider = "prisma-client-js"
}
datasource db {
provider = "postgresql"
url = env("DATABASE_URL")
}
model User {
id Int @id @default(autoincrement())
email String @unique
name String
password String
role Role @default(USER)
createdAt DateTime @default(now())
updatedAt DateTime @updatedAt
deletedAt DateTime? // Soft delete
posts Post[]
sessions Session[]
@@index([email])
@@map("users") // Table name
}
enum Role {
USER
ADMIN
}
model Post {
id Int @id @default(autoincrement())
title String @db.VarChar(255)
body String
published Boolean @default(false)
authorId Int
createdAt DateTime @default(now())
updatedAt DateTime @updatedAt
author User @relation(fields: [authorId], references: [id])
tags Tag[] @relation("PostTags")
@@index([authorId])
@@index([published, createdAt(sort: Desc)])
}
model Tag {
id Int @id @default(autoincrement())
name String @unique
posts Post[] @relation("PostTags")
}
Client Setup
// lib/db.ts
import { PrismaClient } from '@prisma/client'
const globalForPrisma = global as unknown as { prisma: PrismaClient }
export const db = globalForPrisma.prisma ?? new PrismaClient({
log: process.env.NODE_ENV === 'development' ? ['query', 'error'] : ['error'],
})
if (process.env.NODE_ENV !== 'production') globalForPrisma.prisma = db
// Single instance pattern prevents connection exhaustion in dev (Next.js HMR)
Query Patterns
// Find with relations (avoid N+1)
const posts = await db.post.findMany({
where: { published: true, author: { deletedAt: null } },
include: { author: { select: { id: true, name: true } }, tags: true },
orderBy: { createdAt: 'desc' },
take: 20,
skip: (page - 1) * 20,
})
// Upsert
const setting = await db.setting.upsert({
where: { userId_key: { userId, key } },
create: { userId, key, value },
update: { value },
})
// Transaction
const [user, post] = await db.$transaction([
db.user.update({ where: { id: userId }, data: { postCount: { increment: 1 } } }),
db.post.create({ data: { title, body, authorId: userId } }),
])
// Interactive transaction (for complex logic)
const result = await db.$transaction(async (tx) => {
const user = await tx.user.findUniqueOrThrow({ where: { id: userId } })
if (user.balance < amount) throw new Error('Insufficient balance')
await tx.user.update({ where: { id: userId }, data: { balance: { decrement: amount } } })
return tx.payment.create({ data: { userId, amount } })
})
// Raw SQL for complex queries
const stats = await db.$queryRaw<{ date: Date; count: bigint }[]>`
SELECT date_trunc('day', created_at) as date, COUNT(*) as count
FROM posts
WHERE created_at > ${thirtyDaysAgo}
GROUP BY 1 ORDER BY 1
`
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.
- 4d ago First seen · 159 lines · 45 tokens per session scan A becb0744f050
prisma-orm is a skill published in the GitHub repository cohen-liel/hivemind (108 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 1,189 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
business-intelligence
Use when a metric (revenue, MRR, margin) needs defining once in a governed semantic layer so every dashboard, report and agent returns the same number, or when an LLM must answer data questions in plain language without hallucinating SQL. NOT chart layout (that is dashboard), NOT which KPIs to track (that is…
codemap
Query codebase structure via SQLite instead of scanning files. Use when exploring code, finding where symbols are defined, tracing who imports what, listing components / hooks / CSS variables / deprecated symbols, walking dependency or call graphs, or auditing structural changes on a PR.
drizzle-orm
Drizzle ORM patterns for TypeScript. Type-safe SQL queries, schema definitions, migrations, and relational queries. Use when building type-safe database layers in TypeScript projects.
pre-landing-review
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when explicitly asked for the specialized pre-landing workflow. Product /review requests are handled by BitFun's unified Review mechanism instead.…
data-warehouse-experimentation
Running experiments out of the data warehouse instead of via dedicated experiment platforms. SQL-based assignment, exposure logging discipline, metric definitions in dbt models, statistical analysis in SQL or Python, variance reduction with CUPED, sequential testing, and the operational tradeoffs vs platforms like…
postgres
Use this skill for any PostgreSQL database work — table design, indexing, data types, constraints, extensions (pgvector, PostGIS, TimescaleDB), search, and migrations. Trigger when user asks to: Design or modify PostgreSQL tables, schemas, or data models Choose data types, constraints, indexes, or partitioning…