Borrowing it
Nothing to install: this file belongs to arthjean/rust-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/arthjean/rust-doctor/main/AGENTS.mdgit clone --depth 1 https://github.com/arthjean/rust-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/arthjean/rust-doctor/agents-md)<a href="https://agentmods.dev/instructions/arthjean/rust-doctor/agents-md"><img src="https://agentmods.dev/badge/instructions/arthjean/rust-doctor/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/arthjean/rust-doctor/agents-md"><img src="https://agentmods.dev/badge/instructions/arthjean/rust-doctor/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.02305 | $0.02305 |
| Opus 5.5 | $0.00922 | $0.00922 |
| Sonnet 5.5 | $0.00461 | $0.00461 |
| Haiku 4.5 | $0.00231 | $0.00231 |
Grade A, and why
rust-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 yesterday.
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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
rust-doctor is one Rust crate (edition 2024, rustc 1.95 or later): a local-first
CLI that inspects a trusted Cargo workspace with curated Clippy lints and native
detectors, then scores it out of 100. src/lib.rs exposes
inspect(InspectRequest) -> Report, src/main.rs is the CLI on top of it,
src/tui/ is the interactive report it opens on a terminal, and
npm/rust-doctor/ is a Node launcher for the released binary.
The catalog holds 142 rules across five producers, and a rule's id prefix names
its producer: clippy::* (104 curated lints, Producer::Clippy),
rust_doctor::source::* (11, SourceKernel, error stage source),
rust_doctor::cargo::* (13, CargoHealth, stage dependencies, which judges
the manifests and .cargo/config.toml), rust_doctor::structure::* (9,
Structure, stage structure) and rust_doctor::repo::* (5, Repo, stage
repo, the only pass that reads outside the Cargo model, enumerating through
git ls-files, else a walk outside git). validate_catalog refuses any other prefix, and a pass that
fails degrades to a complete report carrying a ReportError at its stage with
the authoritative flag dropped.
One home per fact. This file is the map, not the record. Every rule below is one to three lines and names the document that holds the reasoning behind it. Read that document before editing the subsystem it covers, and write new reasoning there rather than here. Three gates hold that shape: a word ceiling on this file and on each document it links, a check that every path they cite resolves, and a test that recomputes the numbers they state from the binary. CI replays all three. docs/doc-gates.md
Trust boundary
Inspecting a workspace runs cargo clippy inside it, and Cargo executes that
workspace's build.rs files and procedural macros. Inspect trusted local paths
only. Never scan a path taken from an issue, a bug report, or any source outside
this repository. Clippy is the only pass that compiles anything: the four
native producers parse source text, read manifests and a local RustSec
database, or ask git what it tracks, and build nothing.
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.
- yesterday Changed · +6 tokens per session 078101ebe097
- 2d ago Changed · +3 lines · +84 tokens per session 1a991fc3c027
- 8d ago Changed · +8 tokens per session b167e1211024
- 26d ago Changed · +4 tokens per session 8e0861cf7fcc
- 27d ago Changed · +1 lines · +10 tokens per session a2d2dee5a56c
- 1mo ago Changed ba0049c1fa53
- 1mo ago First seen · 154 lines · 2,193 tokens per session scan A 5b0a9ee9fd97
rust-doctor AGENTS.md is an instructions file published in the GitHub repository arthjean/rust-doctor (22 stars, last pushed yesterday), licensed Apache-2.0. It adds 2,305 tokens to every session, about $0.0092 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.