AGENTS.md@mirrord/protocolA
AGENTS.md@mirrord/protocol from metalbear-co/mirrord is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add metalbear-co/mirrord/mirrord/protocol/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/protocol/AGENTS.md- Versions recorded
- 3
- Latest version
- git:20261028.be6a47a, committed Oct 28, 2026
- First version recorded
- Mar 23, 2026
- Size
- 1,347 bytes
- Repository stars
- 5,404
- 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-protocol` ## Backwards Compatibility The protocol defines the messages that layer, intproxy, agent, and operator send to each other. These components ship independently, so we must make sure that they are able to talk to each other even when running mismatched versions. The wire format is generated by the Rust types layouts through `bincode`, so the declarations in this crate _are_ the wire format. **Safe changes**: - Renaming types, fields, or variants (bincode doesn't use names). - Changing a field type only if the bincode representation stays the same. - Adding a new enum variant **at the end**, gated by a negotiated protocol version. - Code changes that don't affect the wire representation. **Breaking changes**: - Adding a field to a struct. - Changing `T` to/from `Option<T>`. - Reordering fields in a struct. - Reordering enum variants. Version checks are defined as `LazyLock<VersionReq>` constants near the types they protect. Consumers use `SwitchProtocolVersion` to negotiate. ## CI and Versioning Rules - This crate is versioned **independently** from the rest of the workspace. …
Read the whole file at its exact version.
How to install
mdr add metalbear-co/mirrord/mirrord/protocol/AGENTS.md@sha256:67b9a3a6dd230891The 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_ge2woduvvpnghspm)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Mar 23, 2026 and Oct 28, 2026, about one every 109 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,347 B | A | view · diff |
| git:20260803.3f140f7 | 2026-08-03 | 3f140f7 | 1,327 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 (1347 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,404 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ge2woduvvpnghspm GET https://markdownregistry.com/api/v1/resolve?ref=metalbear-co/mirrord/mirrord/protocol/AGENTS.md GET https://markdownregistry.com/api/v1/blob/67b9a3a6dd230891d89432a2fd99e20d52a9659b0a770fe1ce5a7e51ad5591f3
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.