vault-recall SKILL.md skillA
vault-recall from jayantak/vaultmem is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jayantak/vaultmem/vault-recall@git:20260807.1910e60Pins git:20260807.1910e60 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jayantak/vaultmem
- Path
skills/vault-recall/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260807.1910e60, committed Aug 7, 2026
- First version recorded
- Jul 24, 2026
- Size
- 11,557 bytes
- Repository stars
- 3
- License
- MIT
Check the vault before you re-derive. Trigger before reconstructing a past decision, root cause, incident, architecture rationale, or "why is it built this way" — even when no memory question is asked — and on explicit lookups ("what do I know about X", "check my notes"). Not for what the code does now; that's the repo.
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
<!-- CANONICAL SOURCE: this repo (jayantak/vaultmem). The dotfiles copy under agents-source/skills/ is synced FROM here — edit this file, not that one. --> # vault-recall — check before you re-derive Your Obsidian vaults **are** your agent-memory layer. This skill is the read side: find what is already written down before spending tool calls reconstructing it. Writing new knowledge back is `vault-capture`; keeping the vault healthy is `vault-curate`; per-thread working state is `session`. ## The reflex Before you investigate a past decision, root cause, or incident, explain "why is it built this way," or spend more than a couple of tool calls reconstructing project or people context — **search the vault first**. - It is ~60ms and ~700 tokens. That is cheaper than reading two files, so a miss costs nearly nothing and the default is to check, not to skip. - Grepping the repo tells you *what* the code does. The vault tells you *why*, and the history the code cannot show. - Do not trust "I already sort of know this" for a past decision. That is how a stale or invented answer ships. **Negative trigger — current code or behavior is the repo, never the vault.** …
Read the whole file at its exact version.
How to install
mdr add jayantak/vaultmem/vault-recall@sha256:f5fec38fe1f3fad8The line at the top of this page pins the label git:20260807.1910e60, 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_stjflijpx7qlvwg5)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 24, 2026 and Aug 7, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260807.1910e60 latest | 2026-08-07 | 1910e60 | 11,557 B | A | view · diff |
| git:20260727.6063466 | 2026-07-27 | 6063466 | 11,011 B | A | view · diff |
| git:20260724.ef729e3 | 2026-07-24 | ef729e3 | 11,635 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 (11557 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
jayantak/vaultmem · 3 stars · license MIT · pushed 2026-10-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_stjflijpx7qlvwg5 GET https://markdownregistry.com/api/v1/resolve?ref=jayantak/vaultmem/vault-recall GET https://markdownregistry.com/api/v1/blob/f5fec38fe1f3fad86180ab5002242f45327881887be09b9414591710613dd2ef
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.