AGENTS.md@mirrord/operatorA
AGENTS.md@mirrord/operator from metalbear-co/mirrord is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add metalbear-co/mirrord/mirrord/operator/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/operator/AGENTS.md- Versions recorded
- 3
- Latest version
- git:20261028.be6a47a, committed Oct 28, 2026
- First version recorded
- Aug 3, 2026
- Size
- 2,572 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-operator` ## Overview `mirrord-operator` is the crate that both the CLI and operator depend on for shared types: - `feature = "crd"`: the Rust types that define CRD specs and statuses, including `schemars` schema generation. - `feature = "client"`: the operator API client used by the CLI to check operator status, create/connect sessions, and create some CRDs. ## Command Reference ```bash CARGO_BUILD_WARNINGS=deny cargo clippy -p mirrord-operator --all-targets --all-features --keep-going -- -Wclippy::indexing_slicing # CI also checks the `crd` feature on its own cargo check -p mirrord-operator --features crd ``` ## Modifying a CRD When modifying a CRD definition run the `generate_helm_crd_yaml` test in the operator repo to update the generated helm charts. ```bash cargo test -p operator-crd generate_helm_crd_yaml -- --ignored --nocapture ``` Kubernetes drops the fields an installed CRD's schema doesn't know, so a CRD change only shows on a cluster whose CRDs were generated from it. A CRD whose objects the operator finalizes also goes in `FINALIZED_CRDS` …
Read the whole file at its exact version.
How to install
mdr add metalbear-co/mirrord/mirrord/operator/AGENTS.md@sha256:5e85ead2b0622552The 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_zjqvjbaxdt3du56o)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 3, 2026 and Oct 28, 2026, about one every 43 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 | 2,572 B | A | view · diff |
| git:20260803.3f140f7 | 2026-08-03 | 3f140f7 | 2,013 B | A | view · diff |
| git:20260803.ba273ff | 2026-08-03 | ba273ff | 9 B | B | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (2572 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_zjqvjbaxdt3du56o GET https://markdownregistry.com/api/v1/resolve?ref=metalbear-co/mirrord/mirrord/operator/AGENTS.md GET https://markdownregistry.com/api/v1/blob/5e85ead2b062255235ccca8cbfe0d09d99526a7aef2ea733d7808fc78126247f
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.