Borrowing it
Nothing to install: this file belongs to jrgilbertson/the-rookery. 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/jrgilbertson/the-rookery/main/AGENTS.mdgit clone --depth 1 https://github.com/jrgilbertson/the-rookeryWrote 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/jrgilbertson/the-rookery/agents-md)<a href="https://agentmods.dev/instructions/jrgilbertson/the-rookery/agents-md"><img src="https://agentmods.dev/badge/instructions/jrgilbertson/the-rookery/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/jrgilbertson/the-rookery/agents-md"><img src="https://agentmods.dev/badge/instructions/jrgilbertson/the-rookery/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.00451 | $0.00451 |
| Opus 5 | $0.00226 | $0.00226 |
| Sonnet 5 | $0.00090 | $0.00090 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
the-rookery 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 10d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Agent Guidance
Private and generated artifacts
This is a public open-source repository. Its working directory holds only this repository's own source, tests, docs, and configuration. Anything generated for the user rather than for the repo, along with its supporting files (builders, renders, previews, inspection files, dependency links), goes in a per-run temporary directory outside the working directory, and final artifacts go only to an explicitly approved external or private destination.
The root outputs/ directory remains ignored as a privacy safeguard for older
Codex Desktop and similar tooling that may write generated artifacts there. It
is not part of the current workflow or an approved storage location.
Before staging or committing, inspect all untracked paths and confirm that no personal or business artifacts are present.
Working artifacts
Keep plans, brainstorms, ideation, raw dogfood notes, and point-in-time reports
in the ignored working paths named in .gitignore. They may live for the life
of a worktree, but the final pull request and default branch must not contain
or depend on them. Preserve the outcome in its canonical home: code and tests
for behavior, an ADR for a lasting architectural choice, docs/solutions/ for
a reusable learning, or the current root RELEASING.md for operating and
shipping procedures.
Research is durable only when the repository will maintain it as a current source. Keep temporary audits and findings with the issue, pull request, or other reporting system. When a source issue exists, record material scope changes and follow-up work there before merge; a routine completion summary or copy of the plan is unnecessary.
Documented solutions and vocabulary
docs/solutions/ holds documented solutions to past problems, covering bugs,
best practices, and workflow learnings, organized by category with YAML
frontmatter (module, tags, problem_type). Relevant when implementing or
debugging in an area a learning already covers.
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.
- 10d ago First seen · 45 lines · 451 tokens per session scan A bda97ff5207e
the-rookery AGENTS.md is an instructions file published in the GitHub repository jrgilbertson/the-rookery (4 stars, last pushed today), licensed MIT. It adds 451 tokens to every session, about $0.0023 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.