AGENTS.md@evals/fixtures/legacy-rangeA
AGENTS.md@evals/fixtures/legacy-range from evolvehq/docflow is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add evolvehq/docflow/evals/fixtures/legacy-range/AGENTS.md@git:20260913.52621c7Pins git:20260913.52621c7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- evolvehq/docflow
- Path
evals/fixtures/legacy-range/AGENTS.md- Versions recorded
- 2
- Latest version
- git:20260913.52621c7, committed Sep 13, 2026
- First version recorded
- Sep 4, 2026
- Size
- 1,237 bytes
- Repository stars
- 16
- License
- MIT
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
# AGENTS.md Guidance for coding agents working in this repository. ## Hard rules when editing ADRs - **One decision per ADR.** Splits become new ADRs that supersede. - **Status lifecycle:** `Proposed -> Accepted -> Implemented -> (Superseded | Deprecated)`. - **Capability ADR section order:** metadata -> Context -> Capability statement -> User stories / scenarios -> Acceptance criteria -> Out of scope -> Open questions -> References -> Revision History -> Approvals. - **Technology ADR section order:** metadata -> Context -> Decision -> Rationale -> Consequences -> Acceptance criteria -> Out of scope -> Open questions -> References -> Revision History -> Approvals. - **Shape is the number range.** Capability ADRs are numbered below `0100`; technology ADRs from `0100` onwards. The technology template sits at the boundary as `adr/0100-template.md`. - **Acceptance criteria are testable and numbered.** - **ADRs are internal artefacts — never user-visible.** ## Plan folder `plan/todo/NNNN-<slug>.md` is pending work; `git mv` to `plan/done/<YYYY-MM-DD>-<slug>.md` is the completion event. ## Reporting …
Read the whole file at its exact version.
How to install
mdr add evolvehq/docflow/evals/fixtures/legacy-range/AGENTS.md@sha256:d18ac880596926c1The line at the top of this page pins the label git:20260913.52621c7, 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_dyqaugsimuehdmcv)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 4, 2026 and Sep 13, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260913.52621c7 latest | 2026-09-13 | 52621c7 | 1,237 B | A | view · diff |
| git:20260904.f02e0fb | 2026-09-04 | f02e0fb | 1,119 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1237 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
evolvehq/docflow · 16 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dyqaugsimuehdmcv GET https://markdownregistry.com/api/v1/resolve?ref=evolvehq/docflow/evals/fixtures/legacy-range/AGENTS.md GET https://markdownregistry.com/api/v1/blob/d18ac880596926c16311424f9aee2bbfef3e94b10878b003b7fe8b0452e23d8b
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.