spec-provenance-review skillA
spec-provenance-review is agent-read markdown (skill) from different-ai/openwork: Flag concrete false-positive proof introduced by changed specs, not test helper or channel preferences. Advisory only; never gates Warden clearance..
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
Review changes under `evals/specs/**` and `evals/worlds/**` for one question: does this diff let a spec pass while the specific behavior it claims to test is broken? Test code has a different purpose from production code. Review the validity of its evidence, not production hardening, abstraction, style, or preferred helper usage. Channel conventions in `evals/README.md` are authoring guidance; a channel mismatch alone is not a finding. Report a MEDIUM (advisory) finding only when ALL of these hold: - The changed lines introduce or materially worsen the gap. - The spec bypasses the behavior under test or asserts evidence unrelated to that behavior. - You can identify a concrete broken behavior that would still pass, grounded in the spec and relevant implementation. A hypothetical possibility or the availability of a different helper is insufficient. Examples worth reporting: - A spec claims a person can submit a form, but directly invokes the API and never submits through the UI, so broken form wiring is not exercised. - A spec claims a save persists data, but only asserts the seeded value and never observes the result of saving. …
Read the whole file at its exact version.
How to install
mdr add different-ai/openwork/spec-provenance-review@git:20260909.89c48damdr add different-ai/openwork/spec-provenance-review@sha256:b4ffdf07ea4fa94cPin 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_xtnhskjy373wp3bt)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260909.89c48da latest | 2026-09-09 | 89c48da | 2,937 B | A | view · diff |
| git:20260904.fdbd4e2 | 2026-09-04 | fdbd4e2 | 2,735 B | A | view · diff |
| git:20260904.93a142a | 2026-09-04 | 93a142a | 1,984 B | A | view · diff |
| git:20260903.d28b267 | 2026-09-03 | d28b267 | 2,073 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 (2937 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
different-ai/openwork · 23,724 stars · license NOASSERTION · pushed 2026-09-25 · branch dev
API
GET https://markdownregistry.com/api/v1/artifacts/art_xtnhskjy373wp3bt GET https://markdownregistry.com/api/v1/resolve?ref=different-ai/openwork/spec-provenance-review GET https://markdownregistry.com/api/v1/blob/b4ffdf07ea4fa94c69d790d84c0dd97683cc42de5b79db519758806a58c7db98
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.