attic-review skillA
attic-review is agent-read markdown (skill) from nishikantaray/attic: Check which stashed items may no longer match the code, and resolve them. Use when the user says "review the attic", "what's stale", "is the attic still accurate", "check the attic against the code", "verify this finding", or after a big refactor, rebase or merge that may have invalidated earlier findings. This is about whether stashed knowledge is still TRUE; use attic-doctor for structural damage and attic-prune for items that are merely old..
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 the attic for stale knowledge
First, in the same shell command as anything below, locate the script:
```bash
ATTIC_JS=$(ls -d "${CODEX_HOME:-$HOME/.codex}"/plugins/cache/attic/attic/*/skills/attic/scripts/attic.js "${CODEX_HOME:-$HOME/.codex}"/skills/attic/scripts/attic.js "$HOME"/.agents/skills/attic/scripts/attic.js .agents/skills/attic/scripts/attic.js 2>/dev/null | sort -V | tail -1)
```
Argument: `$ARGUMENTS` (a slug to verify directly, or empty to list).
## Listing what needs a look
```bash
node "$ATTIC_JS" review
```
Each item comes back with a status and the reason for it:
| Status | Means |
|---|---|
| `possibly-stale` | A file the item cites has changed since it was recorded. |
| `needs-review` | A cited file is gone, or the item is a workaround, or someone flagged it. |
| `unknown` | No provenance to check it against. |
Items stashed before 1.6 have no provenance and are hidden by default, since
listing an entire existing attic as suspect is noise. `--all` includes them.
## What these statuses do NOT mean
`possibly-stale` means **a file moved under this finding**, not that the
…Read the whole file at its exact version.
How to install
mdr add nishikantaray/attic/attic-review@v1.6.1mdr add nishikantaray/attic/attic-review@sha256:b530432907e7a630Pin 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_vzoesaza4zlg4g4t)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.6.1 latest | 2026-09-23 | ec26888 | 2,987 B | A | view · diff |
| v1.6.0 | 2026-09-18 | e3fa82c | 2,987 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 (2987 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
nishikantaray/attic · 5 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vzoesaza4zlg4g4t GET https://markdownregistry.com/api/v1/resolve?ref=nishikantaray/attic/attic-review GET https://markdownregistry.com/api/v1/blob/b530432907e7a630373e23a9379b8882d70103a3956a670e981e4881d3b407d1
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 nishikantaray/attic
Every file in nishikantaray/attic