AGENTS.md@tests/skill-eval-cell/fixtures/setup-instructions-coveredA
AGENTS.md@tests/skill-eval-cell/fixtures/setup-instructions-covered from everyinc/compound-engineering-plugin is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add everyinc/compound-engineering-plugin/tests/skill-eval-cell/fixtures/setup-instructions-covered/AGENTS.md@git:20260903.415181dPins git:20260903.415181d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- everyinc/compound-engineering-plugin
- Path
tests/skill-eval-cell/fixtures/setup-instructions-covered/AGENTS.md- Versions recorded
- 1
- Latest version
- git:20260903.415181d, committed Sep 3, 2026
- Size
- 1,157 bytes
- Repository stars
- 25,969
- 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
# Widget service ## Layout ``` src/ service code tests/ bun tests docs/solutions/ documented solutions to past problems, by category, with YAML frontmatter (module, tags, problem_type); relevant when working in a documented area ``` ## Working agreement - Run `bun test` before opening a PR. - After a solved, verified problem, automatically invoke the `ce-compound` skill with `mode:non-interactive` at the completion checkpoint only when the work produced durable project reasoning that is not readily recoverable from the final code, tests, types, comments, or existing documentation, and losing it would plausibly cause recurrence, material risk, or substantial rediscovery. Apply this counterfactual: if the learning document disappeared, would a future engineer reading the final implementation still be likely to repeat the mistake or redo substantial investigation? If not, do not invoke it. Completion, effort, and diff size alone are not enough. Capture at the checkpoint so a qualifying learning can ship in the PR that produced it, and only where the repository treats captured learnings as tracked, committed knowledge.
Read the whole file at its exact version.
How to install
mdr add everyinc/compound-engineering-plugin/tests/skill-eval-cell/fixtures/setup-instructions-covered/AGENTS.md@sha256:13f1d084d0f59f50The line at the top of this page pins the label git:20260903.415181d, 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_s4vymhc45jfr3hph)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 3, 2026.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1157 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
everyinc/compound-engineering-plugin · 25,969 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_s4vymhc45jfr3hph GET https://markdownregistry.com/api/v1/resolve?ref=everyinc/compound-engineering-plugin/tests/skill-eval-cell/fixtures/setup-instructions-covered/AGENTS.md GET https://markdownregistry.com/api/v1/blob/13f1d084d0f59f5078bce6b79ec45c2da9db73163d371625cfbc9b373eb4b6dd
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.