AGENTS.md@crates/zeph-a2aA
AGENTS.md@crates/zeph-a2a 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-a2a/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-a2a/AGENTS.md- Versions recorded
- 2
- Latest version
- git:20260714.426058a, committed Jul 14, 2026
- First version recorded
- Jun 6, 2026
- Size
- 1,662 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-a2a Guide Protocol client/server work for A2A lives here. - Start with crate-local checks: `cargo build -p zeph-a2a`, `cargo nextest run -p zeph-a2a`, `cargo clippy -p zeph-a2a --all-targets -- -D warnings`. - Read `specs/014-a2a/spec.md` before changing discovery, trust policy, or IBCT; honor its `## Key Invariants` and `NEVER` sections. - Keep changes isolated to A2A transport, discovery, JSON-RPC, and server behavior unless a shared API truly requires cross-crate edits. - Preserve protocol-facing behavior unless the task explicitly calls for a spec-aligned change. - The trust anchor for `AgentCard` signature verification is only the operator-configured `[a2a_client].trusted_agent_keys` store — never a card-supplied `jku` URL (self-signed-forgery + SSRF risk). - IBCT tokens (`ibct.rs`) are HMAC-signed bearer credentials scoped to `task_id` + endpoint origin — never log or dump a raw token, and keep `IbctKey`/`IbctKeyConfig` on hand-written `Debug`/`Serialize` impls that redact `key_hex`/`key_bytes`; a derived impl reopens the leak (#6005, #6165). …
Read the whole file at its exact version.
How to install
mdr add bug-ops/zeph/crates/zeph-a2a/AGENTS.md@sha256:dc0053153799104cThe 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_u2i2tgcm7fu26q77)
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,662 B | A | view · diff |
| git:20260606.583c571 | 2026-06-06 | 583c571 | 570 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1662 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_u2i2tgcm7fu26q77 GET https://markdownregistry.com/api/v1/resolve?ref=bug-ops/zeph/crates/zeph-a2a/AGENTS.md GET https://markdownregistry.com/api/v1/blob/dc0053153799104c6854f6173facc3a7fac0f54f1e5a3336fa8728c82e1c5969
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.