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 rules/krivoox/agent-stack-template/projectgit clone --depth 1 https://github.com/krivoox/agent-stack-templateWhat 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.00656 | $0.00656 |
| Opus 5 | $0.00328 | $0.00328 |
| Sonnet 5 | $0.00131 | $0.00131 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
project 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 2d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project contract
Full guide: AGENTS.md. This rule is the always-loaded summary; do not
duplicate detail here, point to the document that owns it.
Work type
Classify first (AGENTS.md → "Every turn"). Open that guide only.
- New behaviour with a domain rule → spec Accepted or Shipped, then
docs/guides/new-feature.md - New behaviour without a domain rule → same guide; skip tests and
domain/. Do not invent a function to TDD - Wrong current behaviour →
docs/guides/bugfix.md - Same behaviour, new shape →
docs/guides/refactor.md - Tooling / deps / CI / docs-only →
docs/guides/chore.md - Problem without a spec →
product-manager, no product code
If a feature spec is Draft, do not write product code. TDD applies only when
the change adds or breaks a domain rule — AGENTS.md → "Definition of Done".
Sources of truth
When they conflict, this order wins. Open a file only if this turn needs it.
docs/specs/<feature>.md— business rules. Never invent one.docs/architecture.md— when a layer, auth, data or performance boundary movesdocs/stack.md— when adding or substituting a dependencydocs/adr/— accepted decisions, when that decision is in playDESIGN.md— UI only
If a spec lacks the detail you need, update the spec before writing code.
Stack (do not substitute without an ADR)
Next.js App Router · React · TypeScript strict · Better Auth · Prisma + PostgreSQL · Zod + React Hook Form · TanStack Query · Zustand (UI state only) · Tailwind + shadcn/ui · Vitest.
Next.js in this repo may differ from your training data. Check
node_modules/next/dist/docs/ before using an API you are unsure about.
Layers
New behaviour with a domain rule (not every turn):
spec → domain tests → domain → services → actions → UI
src/domain/**,src/features/*/domain/**— pure. No Next, React, Prisma or ambient clock.src/features/*/services/**— the only place Prisma is called.src/features/*/actions/**—defineAction/defineWorkspaceActiononly.src/app/**— thin routes: compose, do not compute.src/lib/env.ts— the only reader ofprocess.env.
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.
- 2d ago First seen · 65 lines · 656 tokens per session scan A ba52b5a97376
project is a cursor rule published in the GitHub repository krivoox/agent-stack-template (30 stars, last pushed 12d ago), licensed MIT. It adds 656 tokens to every session, about $0.0033 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 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.