AGENTS.md@crates/zeph-channelsA
AGENTS.md@crates/zeph-channels 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-channels/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-channels/AGENTS.md- Versions recorded
- 2
- Latest version
- git:20260714.426058a, committed Jul 14, 2026
- First version recorded
- Jun 6, 2026
- Size
- 981 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-channels Guide CLI and chat-channel adapters live here. - Start with crate-local checks: `cargo build -p zeph-channels`, `cargo nextest run -p zeph-channels`, `cargo clippy -p zeph-channels --all-targets -- -D warnings`. - Keep changes isolated to channel adapters, rendering, and streaming behavior unless shared channel traits require coordinated edits. - Secrets (Telegram bot token, webhook secrets) are resolved exclusively from the age vault at startup — never from env vars, config files, or hardcoded values. - Validate formatting and rendering changes against existing markdown and channel tests. - Outbound API calls in Telegram/Discord/Slack must go through the shared `common::http_retry::send_with_retry` helper (429 retry-with-backoff) rather than hand-rolled retry logic — see `discord/rest.rs`, `slack/api.rs`, `telegram_api_ext.rs` (#6100, #6113). - If external behavior changes, update `crates/zeph-channels/README.md` and the relevant channel docs.
Read the whole file at its exact version.
How to install
mdr add bug-ops/zeph/crates/zeph-channels/AGENTS.md@sha256:1e237800c2a2d147The 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_lbgxkuwfos7l5ryq)
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 | 981 B | A | view · diff |
| git:20260606.583c571 | 2026-06-06 | 583c571 | 720 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (981 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_lbgxkuwfos7l5ryq GET https://markdownregistry.com/api/v1/resolve?ref=bug-ops/zeph/crates/zeph-channels/AGENTS.md GET https://markdownregistry.com/api/v1/blob/1e237800c2a2d147d87b50b72a2b667dcefc2688cfe1abce72d401896457c6b2
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.