intended-vs-implemented skillA
intended-vs-implemented is agent-read markdown (skill) from sathiaai/adversarial-review: Verify what the code actually does against what the docs, roadmap, or handoff claim it does — the code is the source of truth. Use before relying on any documented behavior or status..
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
# Intended vs. implemented Documentation describes intent. Code describes reality. When they disagree, **the code wins**, and the disagreement is itself a finding worth surfacing. ## Why this matters here A roadmap, a handoff, a changelog, or a prior review report can confidently assert that a behavior shipped when it did not — a merge dropped it, a fix was described but implemented differently, or a status was aspirational. Building on the *claim* instead of the *code* propagates the error into your own work. > Worked example (real, this repo): the roadmap stated E3-S2b landed a `do_POST` slow-loris > **read-timeout**. Checking the code on `main` — no `settimeout` on the POST read, no `408`, > no handler `timeout` — and `git log -S '408' -- scripts/mcp_server.py` (empty) proved it > **never landed**. Not a regression (nothing was lost); an overstated status. The fix was > then correctly scoped into the story that actually owns it, and the discrepancy recorded. ## The check 1. **Read the claim** (roadmap status, changelog line, handoff, a "DONE" checkbox). 2. **Read the code that would implement it** — the actual function, the actual test, the …
Read the whole file at its exact version.
How to install
mdr add sathiaai/adversarial-review/intended-vs-implemented@git:20260910.c480f23mdr add sathiaai/adversarial-review/intended-vs-implemented@sha256:d36ea07fed6bd249Pin 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_xvsjetthfxzeo5vg)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260910.c480f23 latest | 2026-09-10 | c480f23 | 2,499 B | A | view · diff |
| git:20260910.3ea871a | 2026-09-10 | 3ea871a | 2,233 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2499 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
sathiaai/adversarial-review · 3 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xvsjetthfxzeo5vg GET https://markdownregistry.com/api/v1/resolve?ref=sathiaai/adversarial-review/intended-vs-implemented GET https://markdownregistry.com/api/v1/blob/d36ea07fed6bd24942007c76243bbdc2e68ed7753eb2c1f5c6261417e382ca55
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.