DESIGN.md@_bmad-output/planning-artifacts/ux-designs/ux-agent-harness-2026-09-23 designA
DESIGN.md@_bmad-output/planning-artifacts/ux-designs/ux-agent-harness-2026-09-23 is agent-read markdown (design) from jakeselby/agent-harness.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Brand and style Agent Harness is direct, inspectable and calm. It leads with what a developer can find out or do, and then states its limits without promotional inflation. This contract governs three surfaces: - the terminal; - the agent's own answers and plans, which the `voice` stance and the Review Card shape; - the landing copy generated from `product.json`. The mark is a dial pointer, meaning stances as a setting. It never counts anything, runtimes or providers, because a count goes stale. The name is a plain category name. A name collision is resolved with the full repository path, not by renaming. Components marked *(planned)* describe the target for a planned PRD requirement, not current output. # Colors No meaning depends on colour. Every status is a text word from a closed set, and colour, where a terminal supports it, only reinforces the word. The sets follow the code's vocabulary (architecture spine, Consistency Conventions): - **Catalog states:** `qualified`, `unqualified`, `planned`, `unsupported`. Documentation says "preview" for an unqualified surface. - **Capability modes:** `instruction`, `instruction-and-hook`, `instruction-and-setting`. …
Read the whole file at its exact version.
How to install
mdr add jakeselby/agent-harness/_bmad-output/planning-artifacts/ux-designs/ux-agent-harness-2026-09-23/DESIGN.md@git:20260924.ef349b6mdr add jakeselby/agent-harness/_bmad-output/planning-artifacts/ux-designs/ux-agent-harness-2026-09-23/DESIGN.md@sha256:c7e893705512e7e1Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_qi4hqfod235v4mlg)
0 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260924.ef349b6 latest | 2026-09-24 | ef349b6 | 5,526 B | A | view · diff |
| git:20260923.47f11bb | 2026-09-23 | 47f11bb | 5,520 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (5526 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
jakeselby/agent-harness · 17 stars · license MIT · pushed 2026-09-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qi4hqfod235v4mlg GET https://markdownregistry.com/api/v1/resolve?ref=jakeselby/agent-harness/_bmad-output/planning-artifacts/ux-designs/ux-agent-harness-2026-09-23/DESIGN.md GET https://markdownregistry.com/api/v1/blob/c7e893705512e7e148b66a3be60692f5508d5a08442e16e9786f80e35473cf07
Your agent 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.