AGENTS.md@crates/zeph-configA
AGENTS.md@crates/zeph-config from bug-ops/zeph is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add bug-ops/zeph/crates/zeph-config/AGENTS.md@git:20260714.426058aPins git:20260714.426058a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- bug-ops/zeph
- Path
crates/zeph-config/AGENTS.md- Versions recorded
- 2
- Latest version
- git:20260714.426058a, committed Jul 14, 2026
- First version recorded
- Jun 6, 2026
- Size
- 1,419 bytes
- Repository stars
- 66
- 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
# zeph-config Guide Configuration structs, TOML loader, `ZEPH_*` env var overrides, validation, and migration helpers live here. Vault secret resolution is handled upstream in `zeph-core`. - Start with crate-local checks: `cargo build -p zeph-config`, `cargo nextest run -p zeph-config`, `cargo clippy -p zeph-config --all-targets -- -D warnings`. - `ZEPH_*` env var overrides are for non-secret values only — secrets are resolved from the age vault, never from env vars or config files. - When adding, renaming, or removing config keys, add a `--migrate-config` migration step so existing configs upgrade (or drop leftover keys with a warning) automatically — see #6218 for the removal case. - Keep config structs, `config/default.toml`, docs, and the `--init` wizard in sync for every new field. - If the config surface changes, update `crates/zeph-config/README.md` and `docs/src/` reference pages. …
Read the whole file at its exact version.
How to install
mdr add bug-ops/zeph/crates/zeph-config/AGENTS.md@sha256:5c6c85b2efd80f54The line at the top of this page pins the label git:20260714.426058a, 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_h655yx45enp4btba)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 6, 2026 and Jul 14, 2026, about one every 38 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260714.426058a latest | 2026-07-14 | 426058a | 1,419 B | A | view · diff |
| git:20260606.583c571 | 2026-06-06 | 583c571 | 823 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1419 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
bug-ops/zeph · 66 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_h655yx45enp4btba GET https://markdownregistry.com/api/v1/resolve?ref=bug-ops/zeph/crates/zeph-config/AGENTS.md GET https://markdownregistry.com/api/v1/blob/5c6c85b2efd80f54fc1f31e55a529f583641d384f0ffb0cb79749fe8dc357c3f
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.