Borrowing it
Nothing to install: this file belongs to denfry/codebase-index. 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/denfry/codebase-index/main/AGENTS.mdgit clone --depth 1 https://github.com/denfry/codebase-indexWrote 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/denfry/codebase-index/agents-md)<a href="https://agentmods.dev/instructions/denfry/codebase-index/agents-md"><img src="https://agentmods.dev/badge/instructions/denfry/codebase-index/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/denfry/codebase-index/agents-md"><img src="https://agentmods.dev/badge/instructions/denfry/codebase-index/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.00677 | $0.00677 |
| Opus 5.5 | $0.00271 | $0.00271 |
| Sonnet 5.5 | $0.00135 | $0.00135 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
codebase-index 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
codebase-index
Use the local codebase index before scanning repository files.
Skill resources: .codex/skills/codebase-index/SKILL.md
Run codebase-index search "<query>" --session <tag> --json for general
questions, or use symbol, refs, impact, and graph for symbol lookup,
references, change impact, and HTML graph export. Use one session tag per
conversation: unchanged evidence you already received comes back as
reused: true, and evidence that changed is listed under memory.invalidated.
Before relying on something read earlier, run
codebase-index verify --session <tag> --json. Search/read commands auto-build
the index when it is missing; run codebase-index update when responses report
stale data.
Versioning Policy
Use Semantic Versioning in the MAJOR.MINOR.PATCH format.
- For fixes, maintenance, documentation, tests, small features, and other
changes that are not broad or substantially alter the product, increment
only
PATCH:1.2.3->1.2.4. - For broad or substantial changes, new major capabilities, or notable changes
to behavior or architecture, increment
MINORand resetPATCH:1.2.3->1.3.0. - Do not increment
MAJOR(for example,1.x.x->2.0.0) unless the user explicitly requests it or explicitly approves a breaking release. - When uncertain, use a
PATCHincrement and do not overstate the scope of the release. - When changing the version, update every canonical version location and the changelog together so release metadata remains consistent.
Fork and Pull Request Workflow
When contributing from a fork, keep the pull request focused and easy to review.
- Add the canonical repository as
upstream; keep the contributor fork asorigin. - Never commit directly to
main. Create a branch from the latestupstream/mainusing<type>/<short-description>. - Keep unrelated changes in separate branches and pull requests. Do not include generated files, build artifacts, local configuration, credentials, or editor-specific files.
- Rebase the branch onto the latest
upstream/mainbefore opening or updating the pull request. Do not mergemaininto the feature branch unless a maintainer explicitly requests it. - Run the relevant tests, linting, formatting, and type checks before pushing.
- Use Conventional Commits and write a pull request description that explains the problem, the solution, verification performed, and any compatibility or migration impact.
- Add user-visible changes to
CHANGELOG.mdunder[Unreleased], but do not change the project version unless a maintainer explicitly requests a release version bump. - Push only the contributor branch to the fork, then open a pull request against
the canonical repository's
mainbranch. Never force-push after review has started unless rewriting the branch is necessary and clearly communicated.
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 Changed · +5 lines · +63 tokens per session 5ec471cab8f2
- 1mo ago First seen · 58 lines · 614 tokens per session scan A 3e68e12d44cc
codebase-index AGENTS.md is an instructions file published in the GitHub repository denfry/codebase-index (9 stars, last pushed 12d ago), licensed MIT. It adds 677 tokens to every session, about $0.0027 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.
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.
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).