Borrowing it
Nothing to install: this file belongs to p-to-q/repo-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/p-to-q/repo-template/main/AGENTS.mdgit clone --depth 1 https://github.com/p-to-q/repo-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/p-to-q/repo-template/agents-md)<a href="https://agentmods.dev/instructions/p-to-q/repo-template/agents-md"><img src="https://agentmods.dev/badge/instructions/p-to-q/repo-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/p-to-q/repo-template/agents-md"><img src="https://agentmods.dev/badge/instructions/p-to-q/repo-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.00758 | $0.00758 |
| Opus 5 | $0.00379 | $0.00379 |
| Sonnet 5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
repo-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 9d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file is the long-form operating guide for coding agents and humans who delegate work to agents.
It is adapted from Wittgenstein's AGENTS.md and cross-filled with repository-first discipline from Jah-yee/cursor-rules. Project-specific codec doctrine has been replaced by a general repository discipline contract.
Operating thesis
The repository is the source of truth. Prompts can start work, but durable contracts live in code, docs, tests, issues, PRs, and decision records.
An agent should optimize for:
- small, reviewable changes;
- explicit validation;
- no hidden architectural decisions;
- no claims without receipts;
- useful handoff notes when work stalls;
- route deletion when a template lane is not called.
Read order
Before editing, read only the smallest relevant set:
README.md— project route and status.docs/project-scale.md— current profile.docs/router.md— what files/routes are active.docs/contributor-map.md— where things live.docs/engineering-discipline.md— change discipline.docs/agent-rules.md— optional stack/Cursor rules.CONTRIBUTING.md— branch and PR rules.WORKFLOW.md— issue/agent dispatch rules when agent orchestration is in scope.- Any linked
docs/handoff/*.mdor issue body. - ADR/RFC/brief only if the task touches a decision-bearing surface.
Non-negotiables
- Do not invent context that is not in the repo, issue, PR, or handoff brief.
- Do not silently change public API, license, release, security, workflow, agent contract, or label semantics.
- Do not claim tests passed unless you ran them.
- Do not mix unrelated refactors into a feature or fix.
- Do not use generated code as a substitute for a design decision.
- Do not add new machinery to signal seriousness.
- When blocked, leave a precise handoff note with files read, changes made, validation run, and next decision needed.
Decision-bearing surfaces
Treat these as requiring maintainer attention and, for strict projects, ADR/RFC linkage:
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.
- 9d ago First seen · 79 lines · 758 tokens per session scan A 96e03c39b157
repo-template AGENTS.md is an instructions file published in the GitHub repository p-to-q/repo-template (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 758 tokens to every session, about $0.0038 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-31.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.