agentdoctor: Instructions file for Codex

AGENTS.md

agentdoctor AGENTS.md is an instructions file for Codex, OpenCode from youssefsz/agentdoctor. It costs 1,233 tokens per session, scanned A, original, MIT.

A repository instruction file for AgentDoctor, a Rust command-line tool that checks whether repositories are ready for AI coding agents.

In plain words
What is it for?
It guides work on the Rust workspace, command-line features, generated reports, formatting, and tests using repository fixtures.
Why use it?
It sets clear expectations for clean, repeatable changes and prevents quick patches, unfinished code, and unverifiable behavior.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is youssefsz/agentdoctor's own configuration. It tells Codex and OpenCode how to work on agentdoctor itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentdoctor configures →

Reuse

Borrowing it

Nothing to install: this file belongs to youssefsz/agentdoctor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/youssefsz/agentdoctor/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/youssefsz/agentdoctor

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for agentdoctor AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/youssefsz/agentdoctor/agents-md/github.svg)](https://agentmods.dev/instructions/youssefsz/agentdoctor/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/youssefsz/agentdoctor/agents-md"><img src="https://agentmods.dev/badge/instructions/youssefsz/agentdoctor/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.

agentmods 80×15 button for agentdoctor AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/youssefsz/agentdoctor/agents-md"><img src="https://agentmods.dev/badge/instructions/youssefsz/agentdoctor/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,233 This file is loaded in full into every session.
When invoked 1,233 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01233 $0.01233
Opus 5.5 $0.00493 $0.00493
Sonnet 5.5 $0.00247 $0.00247
Haiku 4.5 $0.00123 $0.00123

Measured 1mo ago against content hash ecccf5b9bdf9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agentdoctor 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.

AGENTS.md · 120 lines

How it starts

The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Instructions

Project overview

AgentDoctor is a Rust 2024 CLI-first workspace that audits repositories for AI coding agent readiness. The project must stay clean, deterministic, cross-platform, and maintainable. Treat this as production-quality developer tooling, not a prototype.

Operating principles

  • Prefer the professional, durable solution over a quick patch.
  • Keep changes scoped to the requested behavior and avoid unrelated refactors.
  • Read the relevant code before editing; do not guess when the repository can answer the question.
  • Plan first for ambiguous or multi-file work, then implement.
  • Do not leave dead code, fake stubs, unused helpers, TODO-heavy placeholders, or partial implementations that pretend to be complete.
  • Make behavior verifiable with tests or a clear command-level check.
  • Preserve deterministic output for generated files and reports.

Stack

  • Rust 2024 workspace.
  • clap for CLI parsing.
  • serde, serde_json, and toml for serialization.
  • ignore for repository walking.
  • directories for platform-native config paths.
  • assert_cmd, tempfile, and fixture repos for tests.

Commands

  • format: cargo fmt --all
  • format check: cargo fmt --all -- --check
  • lint: cargo clippy --workspace --all-targets -- -D warnings
  • test: cargo test --workspace
  • build: cargo build --workspace --release

Project structure

  • crates/agentdoctor-engine/ owns scanning, rule execution, scoring, and deterministic init generation.
  • crates/agentdoctor-config/ owns global and project configuration loading, saving, and precedence.
  • crates/agentdoctor-report/ renders already-built reports only.
  • crates/agentdoctor-cli/ owns CLI parsing, prompts, terminal output, exit codes, and user-facing errors.
  • fixtures/ contains regression repositories used by tests.
  • scripts/, install.sh, and install.ps1 contain installer helpers.
  • .github/workflows/ contains CI and release automation.

Architecture boundaries

  • Do not put scanning, rule, scoring, generation, or report-building logic in the CLI crate.
  • Do not make report rendering inspect the filesystem or run scan logic.
  • Do not make config code print, prompt, scan, or render reports.
  • Keep library crates free of terminal styling, prompts, and process exits.
  • Add abstractions only when they remove real duplication or clarify ownership.
  • Prefer explicit domain types and typed errors in library crates.

Read the full file on GitHub · 120 lines

Changes

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.

  1. 1mo ago First seen · 120 lines · 1,233 tokens per session scan A ecccf5b9bdf9

Subscribe to this mod's changes

agentdoctor AGENTS.md is an instructions file published in the GitHub repository youssefsz/agentdoctor (8 stars, last pushed 3mo ago), licensed MIT. It adds 1,233 tokens to every session, about $0.0049 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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,581 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

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.

deepseek-ai/deepseek-harness · 4,261 tokens