intended-vs-implemented SKILL.md skillA
intended-vs-implemented from sathiaai/adversarial-review is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sathiaai/adversarial-review/intended-vs-implemented@git:20260910.c480f23Pins git:20260910.c480f23 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sathiaai/adversarial-review
- Path
skills/intended-vs-implemented/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260910.c480f23, committed Sep 10, 2026
- First version recorded
- Sep 10, 2026
- Size
- 2,499 bytes
- Repository stars
- 3
- License
- MIT
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.
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
# 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@sha256:d36ea07fed6bd249The line at the top of this page pins the label git:20260910.c480f23, 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_xvsjetthfxzeo5vg)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Sep 10, 2026.
| 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-10-15 · 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 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: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.