AGENTS.md@infrastructure/doctorA
AGENTS.md@infrastructure/doctor from docxology/template is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add docxology/template/infrastructure/doctor/AGENTS.md@git:20260706.ade9b57Pins git:20260706.ade9b57 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- docxology/template
- Path
infrastructure/doctor/AGENTS.md- Versions recorded
- 3
- Latest version
- git:20260706.ade9b57, committed Jul 6, 2026
- First version recorded
- May 16, 2026
- Size
- 5,608 bytes
- Repository stars
- 23
- License
- Apache-2.0
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Doctor module — agent reference This document is the agent-facing companion to `SKILL.md` and `README.md`. It is stable across versions; treat each section as a contract. ## Calling sequence Recommended flow for an agent diagnosing and repairing a checkout: ```bash # 1. Run capabilities once to learn what's available. uv run python -m infrastructure.doctor capabilities > /tmp/doctor_caps.json # 2. Diagnose. Parse the JSON for findings + exit code. uv run python -m infrastructure.doctor --json diagnose > /tmp/doctor_diag.json EXIT=$? # EXIT codes: 0 healthy, 1 warn, 2 error, 3 critical, 4 regression, 64 usage. # 3. If anything actionable, dry-run a plan first. uv run python -m infrastructure.doctor --json fix --plan > /tmp/doctor_plan.json # 4. Apply at the appropriate therapy level. uv run python -m infrastructure.doctor --json fix --apply > /tmp/doctor_applied.json # 5. Inspect `applied[*].action_id` to undo selectively if needed. uv run python -m infrastructure.doctor --json undo --action-id "<id>" ``` Every command writes JSON on stdout when `--json` is set, leaving stderr free for progress/refusal messages. Exit codes are stable. ## JSON schema (stable) …
Read the whole file at its exact version.
How to install
mdr add docxology/template/infrastructure/doctor/AGENTS.md@sha256:1ab8a8bbe8c5aa1fThe line at the top of this page pins the label git:20260706.ade9b57, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_fxrlu4xe5tdhhfye)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 16, 2026 and Jul 6, 2026, about one every 26 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260706.ade9b57 latest | 2026-07-06 | ade9b57 | 5,608 B | A | view · diff |
| git:20260606.243a3c4 | 2026-06-06 | 243a3c4 | 5,602 B | A | view · diff |
| git:20260516.97ec6c2 | 2026-05-16 | 97ec6c2 | 5,438 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (5608 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
docxology/template · 23 stars · license Apache-2.0 · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fxrlu4xe5tdhhfye GET https://markdownregistry.com/api/v1/resolve?ref=docxology/template/infrastructure/doctor/AGENTS.md GET https://markdownregistry.com/api/v1/blob/1ab8a8bbe8c5aa1f36892278a8acf97d7a903884cd2b73ad21e53861e96f1a60
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: how to write a good AGENTS.md · AGENTS.md vs CLAUDE.md · which agent file does what.