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.
git clone --depth 1 https://github.com/krivoox/agent-stack-templateWrote 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/rules/krivoox/agent-stack-template/prisma-schema)<a href="https://agentmods.dev/rules/krivoox/agent-stack-template/prisma-schema"><img src="https://agentmods.dev/badge/rules/krivoox/agent-stack-template/prisma-schema/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/rules/krivoox/agent-stack-template/prisma-schema"><img src="https://agentmods.dev/badge/rules/krivoox/agent-stack-template/prisma-schema.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.00000 | $0.00375 |
| Opus 5.5 | $0.00000 | $0.00150 |
| Sonnet 5.5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
prisma-schema 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 1mo 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
Prisma schema
- Tenancy. Every business model carries
workspaceId, a relation withonDelete: Cascade, and an index that starts withworkspaceId. Without the cascade, deleting a workspace orphans rows; without the index, every scoped list is a sequential scan. - Both sides of a relation are declared, with explicit
@relation. - Ids:
@id @default(cuid())for business models. Better Auth models keep the ids the adapter assigns — do not change them. - Timestamps:
createdAt @default(now())andupdatedAt @updatedAton anything a user edits. - Indexes on every field used in a
where,orderByor join. Compound indexes follow query order (@@index([workspaceId, status])). - Uniqueness with
@unique/@@unique. Case-insensitive uniqueness has no direct equivalent — enforce it in the domain and say so in a comment. @@mapto snake_case table names; the Better Auth models must keep the names the adapter expects.
Migrations
npm run db:migratein development; the generated SQL is reviewed, not trusted blindly.- A rename that Prisma renders as drop + add is data loss. Split it: add the column, backfill, then remove the old one in a later migration.
npm run db:pushis for local scratch work only. It never runs against a shared database.
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.
- 1mo ago First seen · 33 lines · 0 tokens per session scan A 36d87e387170
prisma-schema is a cursor rule published in the GitHub repository krivoox/agent-stack-template (31 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 375 tokens. 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 cursor rules, from other repositories
coding-guidelines
You are working on tRPC - a TypeScript-first RPC library that provides end-to-end type safety between client and server. As a TypeScript expert contributing to this library, you should.
upgrade-tests
// ✅ CORRECT: Upgrade package pattern await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
react-query-tests
// ✅ CORRECT: Legacy React Query pattern const ctx = konn() .beforeEach(() => createAppRouter()) .afterEach((ctx) => ctx?.close?.()) .done().
tanstack-react-query-tests
// ✅ CORRECT: Use await using for automatic cleanup await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
test-patterns
// ✅ CORRECT: Use await using for automatic cleanup await using ctx = testServerAndClientResource(router, { client(opts) { return { links: [ httpLink({ url: opts.httpUrl, fetch: mockFetch, }), ], }; }, }).
test-running
When running tests, use the --watch false flag to avoid watch mode.