memory-factcheck skillA
memory-factcheck is agent-read markdown (skill) from leeyudok/agents-scaffold: Fact-check an agent's persistent memory against ground truth — verify each memory's load-bearing claims against code, database, issue tracker and filesystem, correct the stale ones, and report dead ones as archive candidates. Use when memory grows past ~30 files, right after a big stack/infra change (library swap, version upgrade, server migration, schema drop), when two memories seem to contradict each other, or on a "clean up / audit my memory" request..
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
# Memory Fact-Check > Origin: the skill of the same name in [leeyudok/doksam-skills](https://github.com/leeyudok/doksam-skills). > **Deliberately forked** for template bundling — not auto-synced; good improvements are cherry-picked manually. Memory decays. A fact that was true when written becomes false as code, schema and infrastructure move on. **Stale memory is worse than no memory** — an agent reads it and confidently does the wrong thing. This is **not** a structural hygiene pass. Orphan files, duplicate entries, index bloat, broken internal links — those checks compare memory files *to each other*. This skill compares each memory **to the world it describes**: the code, the database, the issue tracker, the filesystem. A memory can be perfectly well-formed, correctly indexed, recently touched — and completely false. Automatic deletion is forbidden. Only a source-of-truth comparison can tell what is dead, and losing an incident lesson is expensive. Hence semi-automatic: **correct freely, archive only with approval, never delete.** ## 1. Locate and inventory Find the memory set. Common locations, in order: …
Read the whole file at its exact version.
How to install
mdr add leeyudok/agents-scaffold/memory-factcheck@git:20260816.a9fd324mdr add leeyudok/agents-scaffold/memory-factcheck@sha256:4b2129ea1ffc3809Pin 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_szaflwhcctlvxhpx)
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 (9229 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
leeyudok/agents-scaffold · 25 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_szaflwhcctlvxhpx GET https://markdownregistry.com/api/v1/resolve?ref=leeyudok/agents-scaffold/memory-factcheck GET https://markdownregistry.com/api/v1/blob/4b2129ea1ffc380987889d4b614b382dca0881ce9ff8927c4fbf5161ffe3519d
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 leeyudok/agents-scaffold
Every file in leeyudok/agents-scaffold