Borrowing it
Nothing to install: this file belongs to InteliGHQ/intelig-agent-playbook. 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/InteliGHQ/intelig-agent-playbook/main/AGENTS.mdgit clone --depth 1 https://github.com/InteliGHQ/intelig-agent-playbookWrote 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/intelighq/intelig-agent-playbook/agents-md)<a href="https://agentmods.dev/instructions/intelighq/intelig-agent-playbook/agents-md"><img src="https://agentmods.dev/badge/instructions/intelighq/intelig-agent-playbook/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/intelighq/intelig-agent-playbook/agents-md"><img src="https://agentmods.dev/badge/instructions/intelighq/intelig-agent-playbook/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.01227 | $0.01227 |
| Opus 5.5 | $0.00491 | $0.00491 |
| Sonnet 5.5 | $0.00245 | $0.00245 |
| Haiku 4.5 | $0.00123 | $0.00123 |
Grade A, and why
intelig-agent-playbook 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 2mo 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Platform — Agent Context
This is the canonical context file. Every agent reads it (Claude Code reads it via the
@AGENTS.mdline inCLAUDE.md; Codex, Cursor, Copilot, Gemini CLI, Aider and others readAGENTS.mdnatively). Keep it lean — it loads on every turn. Put detail in the files it links to, not here.
What you are working on
Fork note — replace this block with your product. One or two sentences: what the system is, the bounded context this repo owns, and its core lifecycle/invariants. Keep it tight; it loads on every turn. Pattern: "A
<kind of system>. This codebase is its<Context>context:<what it does>, moving them through<STATE → STATE → STATE>. Small surface, real invariants."
Example used throughout this repo: a B2B SaaS backend whose Customer context registers a
customer (a company + a primary contact) and moves it through PENDING → ACTIVE → SUSPENDED — a
teaching example for building cleanly with an agent.
Prime directives
- Spec before code. Work is organized by domain: each bounded context lives in
product/domains/<domain>/(itsREADME.mdis the durable description), and keeps its spec-first work-items inproduct/domains/<domain>/work-items/<work-item>/(requirements → design → tasks → acceptance). Read the spec; implement one task at a time; stop at the acceptance gate. Don't invent scope the spec doesn't ask for. - Standards are law. Before writing code in an area, read the matching family in
standards/(start atstandards/STANDARDS_INDEX.md→ it tells you which families apply). Cite the rule ID where it clarifies intent (commit, PR, or a brief code comment, e.g.// DOM-002: factory method, no public constructor). Rule IDs read<FAMILY>-<NNN>— families areARCH DOM CQRS API ES DB TS, each listed instandards/STANDARDS_DIGEST.md(soDOM-002= the 2nd rule in the domain-model family). - Advisory vs enforced. Rules here are advisory. The mandatory ones are enforced by
fitness-function tests (see
standards/architecture.rules.md→ Enforcement Map). If a test would stop you, the rule is not optional. If you keep wanting to break a rule, that's a signal to change the test, not to sneak past it. - Tag work to strategy. Active initiatives are in
product/initiatives.md(the session hook prints them for you). Reference the initiative ID in the commit subject so code links back to why it exists.
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.
- 2mo ago First seen · 78 lines · 1,227 tokens per session scan A f0eeb7bce72b
intelig-agent-playbook AGENTS.md is an instructions file published in the GitHub repository InteliGHQ/intelig-agent-playbook (2 stars, last pushed 4mo ago), licensed MIT. It adds 1,227 tokens to every session, about $0.0049 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-31.
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.