Borrowing it
Nothing to install: this file belongs to brekkylab/backlot. 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/brekkylab/backlot/main/AGENTS.mdgit clone --depth 1 https://github.com/brekkylab/backlotWrote 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/brekkylab/backlot/agents-md)<a href="https://agentmods.dev/instructions/brekkylab/backlot/agents-md"><img src="https://agentmods.dev/badge/instructions/brekkylab/backlot/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/brekkylab/backlot/agents-md"><img src="https://agentmods.dev/badge/instructions/brekkylab/backlot/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.01171 | $0.01171 |
| Opus 5.5 | $0.00468 | $0.00468 |
| Sonnet 5.5 | $0.00234 | $0.00234 |
| Haiku 4.5 | $0.00117 | $0.00117 |
Grade A, and why
backlot 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 13d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Backlot serves enterprise SaaS APIs (Slack, Gmail, Google Drive, GitHub, Jira, and more) over a corpus the user supplies, with per-document ACLs. Fidelity to the real APIs is the point of the project — read this before changing anything.
Fidelity is measured, never assumed
- A divergence from the real vendor API is a bug. A claim about what the real API does needs a measurement against the real service or a quote from the vendor's spec — never memory, never another mock, never this repo's own earlier prose.
- When a validation rule disagrees with a value the code produces, do not assume the rule is wrong. Find which side has an external source first. Widening a pattern to make a test pass has shipped a real bug here before.
- Docstrings that attribute a shape to the real vendor are source attributions. Do not delete or invert them without checking the vendor's spec.
Where a change goes
backlot/routers/— one module per vendor: response shapes, status codes, pagination.backlot/schemas/*.schema.json— the record schema per source.docs/supported-sources.mdand the README source table are downstream of these.backlot/acl.py— which principal sees which document, in the vendor's own terms.backlot/importer/— how a corpus gets in: the bundled set, BYO JSONL,--id-map, the roster.tests/test_<source>.py— written against measured vendor responses.examples/— one self-contained script per service per integration.
Adding a source is never one file. The full checklist lives in issue #89 and is the same every
time: schema, router, ACL mapping, BYO field mapping and ids, tests, SDK example, regenerated
docs, pyproject.toml keywords.
Documentation rules (tests/test_docs.py enforces all of these)
- README.md stays ≤ 180 lines. If a change needs more room, the content belongs in
docs/. - Never state a source count in README.md. Counts go stale; the generated inventory carries the real one.
- Every relative link in every markdown file must resolve on disk. Do not link a path a stacked PR will add later.
docs/supported-sources.mdis generated. Never hand-edit between the generated markers — runpython scripts/gen_docs.py.- Do not describe the served surface as "read-only" in user-facing docs. The wording was removed deliberately.
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.
- 13d ago Changed · +2 lines · +48 tokens per session ad433bbdd201
- 16d ago Changed · +13 lines · +216 tokens per session e0c926676ad1
- 18d ago Changed · +6 lines · +148 tokens per session 0a5fe71728a8
- 1mo ago First seen · 63 lines · 759 tokens per session scan A b4fb4ade991a
backlot AGENTS.md is an instructions file published in the GitHub repository brekkylab/backlot (295 stars, last pushed today), licensed MIT. It adds 1,171 tokens to every session, about $0.0047 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.