Borrowing it
Nothing to install: this file belongs to alipajand/agent-context-doctor. 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/alipajand/agent-context-doctor/main/AGENTS.mdgit clone --depth 1 https://github.com/alipajand/agent-context-doctorWrote 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/alipajand/agent-context-doctor/agents-md)<a href="https://agentmods.dev/instructions/alipajand/agent-context-doctor/agents-md"><img src="https://agentmods.dev/badge/instructions/alipajand/agent-context-doctor/agents-md.svg" alt="Measured on agentmods" 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.00572 | $0.00572 |
| Opus 5 | $0.00286 | $0.00286 |
| Sonnet 5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
agent-context-doctor 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 7d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS — agent-context-doctor
This is a TypeScript Node.js CLI project. You are an implementation agent.
What this project is
agent-context-doctor (acd) is a deterministic CLI that audits agent instruction files
for quality, safety, contradictions, and stale commands. It is not an AI product.
Absolute constraints
Do not do any of the following without explicit approval:
- Add LLM or AI API calls of any kind
- Add telemetry, analytics, or any outbound network calls
- Add authentication or credential handling
- Build a web server, web app, or browser UI
- Change the binary name (
acd) or existing command names (audit,list) - Modify
.acdrcschema in a breaking way - Change the
AuditResultJSON shape in a backward-incompatible way - Write to any file outside the audited repo path (only
--outputwrites are allowed) - Add dependencies that make external network requests
Tech stack
- TypeScript, ESM, Node.js ≥ 18
- pnpm
commander,fast-glob,zod,picocolorsvitestfor tests,tsxfor dev,prettierfor formatting
Commands to run before finishing
pnpm format:check # formatting
pnpm typecheck # TypeScript
pnpm lint # also TypeScript (same as typecheck)
pnpm test # vitest — all tests must pass
pnpm build # tsc compilation to dist/
All five must pass with zero errors before you consider work complete.
Code conventions
- All source files live under
src/; tests undertests/ - Each audit check is a pure function in
src/audit/checks/ - Cross-file logic goes in
auditRepo.ts, not in individual checks - No
anytypes; nots-ignorecomments - Do not add comments that narrate what the code does — only explain non-obvious intent
Safe-write behavior
The only file the tool writes is the optional Markdown report via --output. Paths are
resolved relative to the audited repo root. Do not add any other file-write operations
without approval.
Final report
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.
- 7d ago First seen · 66 lines · 572 tokens per session scan A 6c6f5e203881
agent-context-doctor AGENTS.md is an instructions file published in the GitHub repository alipajand/agent-context-doctor (1 stars, last pushed yesterday), licensed MIT. It adds 572 tokens to every session, about $0.0029 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
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).
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.
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 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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.