Borrowing it
Nothing to install: this file belongs to krivoox/agent-stack-template. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/krivoox/agent-stack-template/main/AGENTS.mdgit 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/instructions/krivoox/agent-stack-template/agents-md)<a href="https://agentmods.dev/instructions/krivoox/agent-stack-template/agents-md"><img src="https://agentmods.dev/badge/instructions/krivoox/agent-stack-template/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.
<a href="https://agentmods.dev/instructions/krivoox/agent-stack-template/agents-md"><img src="https://agentmods.dev/badge/instructions/krivoox/agent-stack-template/agents-md.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.02198 | $0.02198 |
| Opus 5.5 | $0.00879 | $0.00879 |
| Sonnet 5.5 | $0.00440 | $0.00440 |
| Haiku 4.5 | $0.00220 | $0.00220 |
Grade A, and why
agent-stack-template 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 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This is NOT the Next.js you know
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices.
Agent guide
Rename this product in
src/lib/app-config.ts,package.jsonand this file. Everything else is already generic.
What this repository is
A production-shaped starting point for a multi-tenant web application, built so that coding agents produce consistent work without being told the same things twice. Conventions live in files an agent reads automatically, not in a person's head.
The included projects feature is a reference vertical slice, not a
product. Read it, copy its shape, then delete it.
Every turn
Classify before opening a file. Open one matching guide. Do not read the other playbooks, and do not start from the layer walkthrough until the type is known.
| The request is… | Do this | Do not |
|---|---|---|
| A problem, audience or outcome, no spec | product-manager → spec Draft |
write product code |
| Spec exists but is Draft, or has open questions | resolve with the user; domain-architect if the rules are non-trivial |
write product code |
| Spec Accepted or Shipped, new behaviour with a domain rule | new-feature.md | skip the spec |
| Spec Accepted or Shipped, new behaviour with no domain rule (wiring, copy, layout only) | new-feature.md, skip domain tests and domain/ |
invent a domain/ function so TDD has a target |
| Spec and code disagree | say which is wrong; fix that one | invent a third rule |
| Current behaviour is wrong | bugfix.md | start a feature |
| Same behaviour, new shape | refactor.md | change a spec rule |
| Tooling, deps, CI, env, docs-only | chore.md | sneak in behaviour; write a domain test |
| Copy, layout, existing actions | ui-ux-developer |
put rules in React; TDD the markup |
| Infra, migrations, deploy, secrets | devops-engineer |
run destructive commands unasked |
The change does not touch domain/ and adds no business rule |
TDD does not apply. npm run verify is the gate |
invent a test or a domain wrapper |
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 · 170 lines · 2,198 tokens per session scan A be22bee4fb5c
agent-stack-template AGENTS.md is an instructions file published in the GitHub repository krivoox/agent-stack-template (31 stars, last pushed 28d ago), licensed MIT. It adds 2,198 tokens to every session, about $0.0088 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-08-30.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.