AGENTS.md@mirrord/configA
AGENTS.md@mirrord/config from metalbear-co/mirrord is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add metalbear-co/mirrord/mirrord/config/AGENTS.md@git:20261028.be6a47aPins git:20261028.be6a47a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- metalbear-co/mirrord
- Path
mirrord/config/AGENTS.md- Versions recorded
- 2
- Latest version
- git:20261028.be6a47a, committed Oct 28, 2026
- First version recorded
- Mar 23, 2026
- Size
- 1,311 bytes
- Repository stars
- 5,401
- 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
# `mirrord-config`
## Overview
`mirrord-config` holds the config types and their validation, which the CLI and the layer use to decide what features
are enabled and what target to use.
## Plans
Every option records the plan it needs (`oss`, `team`, or `enterprise`, per its docs page) as `x-mirrord-plan` in the
schema, as a `mirrord_config::plan::Plan`: `#[config(plan = Team)]` on `MirrordConfig` fields,
`#[schemars(extend("x-mirrord-plan" = crate::plan::Plan::Team))]` elsewhere. Nested options inherit it, except that
every option under `feature` and every target kind needs its own; tests in `mirrord-mcp` fail on an option without
one.
## Schemas and Docs
The doc comments here are user documentation. They go into `mirrord-schema.json`, and on each release that changes
it, the release workflow publishes them as the configuration reference, onto this repository's `docs` branch.
`<!--${internal}-->` keeps a doc comment out of the reference. `typos` checks this crate's Rust in CI.
After any change to the types or their docs, regenerate the schema, or `schema_file_is_up_to_date` fails. The same
change can reach `mirrord-up-schema.json`, which `mirrord/up/AGENTS.md` covers.
…Read the whole file at its exact version.
How to install
mdr add metalbear-co/mirrord/mirrord/config/AGENTS.md@sha256:25a2f9cffa0fa2f8The line at the top of this page pins the label git:20261028.be6a47a, 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_72ba5evojqtnu76s)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Mar 23, 2026 and Oct 28, 2026, about one every 219 days. Its first recorded version is graded B and its latest A.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.be6a47a latest | 2026-10-28 | be6a47a | 1,311 B | A | view · diff |
| git:20260323.2d81e57 | 2026-03-23 | 2d81e57 | 9 B | B | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1311 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
metalbear-co/mirrord · 5,401 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_72ba5evojqtnu76s GET https://markdownregistry.com/api/v1/resolve?ref=metalbear-co/mirrord/mirrord/config/AGENTS.md GET https://markdownregistry.com/api/v1/blob/25a2f9cffa0fa2f81fabcb0bf5ccef2586897a84aab3dafd2dcd7f1530c5cfa1
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.