fact-check skillA
fact-check is agent-read markdown (skill) from amethystluna/embedded-workbench: Use when reviewing design documents, architecture specs, technical proposals, or plans that make claims about API names, file paths, enum values, counts, or mechanism feasibility — a lightweight claim-by-claim check against the codebase with evidence. Built into embedded-workbench as the fallback when the full logicprobe plugin is not installed. NOT for state machines, protocol/retry logic, or 'always'/'never' behavioral claims that need executable model verification — those require the logicpro.
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
# Fact Check (fallback) Lightweight claim verification built into this plugin. Use it when the full `logicprobe` plugin is not installed — it checks every verifiable claim in a document/plan against the codebase with evidence, without model escalation. ## When to use - Design docs, architecture specs, technical proposals, refactoring plans that name APIs, types, files, enums, counts, or mechanisms. - Proactively when a plan will be approved (plan-mode gate) and logicprobe is unavailable. ## What to verify (per claim) | Claim type | Method | |-----------|--------| | Numeric claims (counts, sizes, frequencies) | `grep -c` / `grep -rn` | | API/type/enum names | Extract actual signatures/values from headers | | File paths and line numbers | Confirm existence and content | | Mechanism feasibility | Check language standard / compiler support | ## Process 1. Enumerate every verifiable claim (quote it verbatim). 2. Verify each against the codebase with evidence (file:line + excerpt). 3. Output per claim: claim → evidence → verdict. ## Output format - **Claim**: <verbatim quote> - **Evidence**: <file:line + grep/read excerpt> - **Verdict**: confirmed | refuted | unverifiable …
Read the whole file at its exact version.
How to install
mdr add amethystluna/embedded-workbench/fact-check@git:20260829.1d4f8bfmdr add amethystluna/embedded-workbench/fact-check@sha256:c58b8fe9b1c52009Pin 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_vpapod33b4g6wezg)
1 badge views in 30 days
Versions
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 (2560 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
amethystluna/embedded-workbench · 12 stars · license MIT · pushed 2026-09-22 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_vpapod33b4g6wezg GET https://markdownregistry.com/api/v1/resolve?ref=amethystluna/embedded-workbench/fact-check GET https://markdownregistry.com/api/v1/blob/c58b8fe9b1c520090770007ba05a11542a272ac5a98881adf32e577338e5dd30
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.
More from amethystluna/embedded-workbench
Every file in amethystluna/embedded-workbench