AGENTS.md@srcA
AGENTS.md@src from bug-ops/zeph is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add bug-ops/zeph/src/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
src/AGENTS.md- Versions recorded
- 2
- Latest version
- git:20260714.426058a, committed Jul 14, 2026
- First version recorded
- Jun 6, 2026
- Size
- 1,346 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
# Root Binary Guide This directory contains the top-level binary wiring for CLI commands, runtime startup, daemon entrypoints, and feature-gated integration points. - Changes here usually coordinate existing crate APIs rather than introducing core logic from scratch. - When adding or changing a feature, provide all integration points: config section, CLI subcommand/argument, TUI command palette entry, `--init` wizard update, `--migrate-config` migration step, live testing playbook in `.local/testing/playbooks/`, and coverage row in `.local/testing/coverage-status.md`. - This directory has multiple parallel session entry points (`runner.rs`, `daemon.rs`, `acp.rs`, `serve/`, plus gateway spawn paths) that each build their own agent/session wiring. Verify new functionality is wired into every entry point that constructs a session, not just the one you're testing — inconsistent cross-entry-point wiring has been the most common defect class in this directory (e.g. #6031/#6032, #5978, #5976, #6169, #6039, #6047, #6102, #6140). - Secrets are never passed via environment variables or flags; all `ZEPH_*` keys are resolved from the age vault at startup. …
Read the whole file at its exact version.
How to install
mdr add bug-ops/zeph/src/AGENTS.md@sha256:4ab59a9312e44e82The 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_bv5rj73bzxctxzuy)
4 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,346 B | A | view · diff |
| git:20260606.583c571 | 2026-06-06 | 583c571 | 882 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1346 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_bv5rj73bzxctxzuy GET https://markdownregistry.com/api/v1/resolve?ref=bug-ops/zeph/src/AGENTS.md GET https://markdownregistry.com/api/v1/blob/4ab59a9312e44e8242ee6822fb4095b315e52cc044c949d667abc79a5fe76cf9
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.