recall SKILL.md skillA
recall from aiyo28/memento-os is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add aiyo28/memento-os/recall@v2.0.1Pins v2.0.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- aiyo28/memento-os
- Path
adapters/codex/skills/recall/SKILL.md- Versions recorded
- 1
- Latest version
- v2.0.1, committed Nov 9, 2026
- Size
- 3,909 bytes
- Repository stars
- 4
- License
- MIT
Session opening ritual. Loads context via L0→L1 protocol, displays briefing with active decisions and pending items, checks for stale artifacts by priority. Triggers: "start session", "what's the context", "where were we", "catch me up".
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
# /recall Load context. Display briefing. Flag staleness. Get to work. ## Steps ### 1. Load L0 — Session Continuity Read `NEXT.md` in the project root. ### 2. Load L1 — Project Context (~600 tokens) Read (skip if missing): - Project `AGENTS.md` - Vault `_context.md` — **top 3 sections only**: Summary + Key Numbers + Active Reasoning Artifacts table. STOP before Doc Index / Decision Log / Open Questions / Related sections. This is the L1 partial read rule. - Peer Card (`People/Self.md` in vault or memory folder) — structured user profile with communication style, decision patterns, strengths, growth areas. Load the **Communication Style** and **Decision Patterns** tables only (~20 lines). Template provided in starter vault. Skip if missing — suggest creating one on first session. ### 3. Seed Activation Check Scan `[S]` entries in the Active Reasoning Artifacts table: - If activation condition appears met → surface in briefing under "Seeds Ready" - If dormant > 90 days → flag for review - When a seed activates, suggest: "This seed is ready. Want to `/decide` on it?" ### 4. Staleness Check Scan `[D]`, `[I]`, `[E]` entries in the Active Reasoning Artifacts table: …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_wcady4aoy2roskux/1ecbe9cdaa4d2c5f17e0196e5760bfa2e971eafba30b686cfb239ef30131545b.json
Then /plugin install recall@markdownregistry-wcady4aoy2roskux in Claude Code. It installs v2.0.1, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add aiyo28/memento-os/recall@sha256:1ecbe9cdaa4d2c5fThe line at the top of this page pins the label v2.0.1, 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_wcady4aoy2roskux)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in aiyo28/memento-os/recall since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of recall from somewhere else? Ask it: where did my recall come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 9, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/recall/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (3909 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
aiyo28/memento-os · 4 stars · license MIT · pushed 2026-11-10 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wcady4aoy2roskux GET https://markdownregistry.com/api/v1/resolve?ref=aiyo28/memento-os/recall GET https://markdownregistry.com/api/v1/blob/1ecbe9cdaa4d2c5f17e0196e5760bfa2e971eafba30b686cfb239ef30131545b
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.
More from aiyo28/memento-os
Every file in aiyo28/memento-os