Borrowing it
Nothing to install: this file belongs to bekirdag/docdex. 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/bekirdag/docdex/main/AGENTS.mdgit clone --depth 1 https://github.com/bekirdag/docdexWrote 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/bekirdag/docdex/agents-md)<a href="https://agentmods.dev/instructions/bekirdag/docdex/agents-md"><img src="https://agentmods.dev/badge/instructions/bekirdag/docdex/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/bekirdag/docdex/agents-md"><img src="https://agentmods.dev/badge/instructions/bekirdag/docdex/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.09725 | $0.09725 |
| Opus 5.5 | $0.03890 | $0.03890 |
| Sonnet 5.5 | $0.01945 | $0.01945 |
| Haiku 4.5 | $0.00972 | $0.00972 |
Grade A, and why
docdex AGENTS.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Use impact analysis for every code change: prefer MCP tools `docdex_impact_graph` / `docdex_dag_export` (IPC/HTTP). If shell networking is blocked, do not use curl; use MCP/IPC instead. If unavailable, state it and pro How it starts
The opening of the file, as written. The whole thing — 560 lines — stays where its author put it; the contents beside it link to each section on GitHub.
---- START OF DOCDEX INFO V0.2.99 ----
Docdex URL: http://127.0.0.1:28491
Use this base URL for Docdex HTTP endpoints.
Health check endpoint: GET /healthz (not /v1/health).
Priority Directives (Mandatory)
- Always use both memory lobes early: docdex_get_profile + docdex_memory_recall; save new facts via docdex_memory_save and new preferences via docdex_save_preference.
- Profile memory is always-on and global; never gate on DOCDEX_ENABLE_MEMORY or repo state. docdex_save_preference must persist (fallback if embeddings/LLM unavailable). If profile calls fail, treat it as a bug.
- Maintain agent-specific profile memory: use your agent_id with docdex_get_profile/docdex_save_preference; store generic self-knowledge (role, tooling, preferences).
- Use impact analysis for every code change: prefer MCP tools
docdex_impact_graph/docdex_dag_export(IPC/HTTP). If shell networking is blocked, do not use curl; use MCP/IPC instead. If unavailable, state it and proceed cautiously. - Apply DAG reasoning for planning: prefer dependency graph facts (impact results and /v1/dag/export) to choose the right change order and scope.
- Use Docdex tools intentionally: docdex_search/symbols/ast for repo truth; docdex_stats/files/repo_inspect/index for index health.
- When session history matters, use conversation-memory tools intentionally: archive/search/read with
docdex_conversation_*, build compact context withdocdex_wakeup, record durable notes withdocdex_diary_*, and inspect temporal graph state withdocdex_kg_*instead of replaying full transcripts. - For folder structure, use docdex_tree instead of raw
rg --files/findto avoid noisy folders. - When you do not know something, run docdex_web_research (force_web=true). Web research is encouraged by default for non-repo facts and external APIs.
- When a Docdex feature makes a task easier/safer, you MUST use it instead of ad-hoc inspection. Examples:
docdex_searchfor context,docdex_open//v1/snippetfor file slices,docdex_symbols/docdex_astfor structure,docdex_impact_graph/docdex_impact_diagnosticsfor dependency safety, anddocdex_dag_exportto review session traces. - For dependency/library docs, run
docdexd libs discover/docdexd libs fetchand search withinclude_libsrather than web searching. - For test execution, use
docdexd run-tests(ordocdexd test run-node) instead of ad-hoc commands when feasible. - For daemon stability triage, prioritize FD hardening checks: startup nofile warning threshold (
DOCDEX_MIN_NOFILE_SOFT), profile lock retry knobs (DOCDEX_PROFILE_LOCK_MAX_ATTEMPTS,DOCDEX_PROFILE_LOCK_RETRY_BASE_MS), installer pressure defaults (DOCDEX_REPO_IDLE_SECONDS,DOCDEX_REPO_HIBERNATE_SECONDS,DOCDEX_REPO_CLEANUP_INTERVAL_SECONDS), anddocs/ops/fd_exhaustion_playbook.md. - For staged-change validation, use
docdexd hook pre-commit. - For MCP client registration, use
docdexd mcp add(or--all) instead of editing configs by hand.
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 · 560 lines · 9,725 tokens per session scan A cda3f31166ad
docdex AGENTS.md is an instructions file published in the GitHub repository bekirdag/docdex (16 stars, last pushed 5d ago), licensed MIT. It adds 9,725 tokens to every session, about $0.0389 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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).
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.