session SKILL.md skillA
session 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/session@git:20260817.76f9246Pins git:20260817.76f9246 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jayantak/vaultmem
- Path
skills/session/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260817.76f9246, committed Aug 17, 2026
- First version recorded
- Jul 24, 2026
- Size
- 23,841 bytes
- Repository stars
- 3
- License
- MIT
Always-active cross-session working memory. Auto-activates every conversation to offer resuming or starting a session. Also triggers on "start a session", "resume", "park this", "save this", "wrapping up", or multi-session/multi-repo work. Routes work to the correct Obsidian vault, groups sessions under a parent Project (epic), and distills durable insights up into the Project note and MOCs at stopping points.
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. --> # session — cross-session working memory The hot layer above the durable Obsidian vaults. Sessions are per-thread worklogs that survive `/clear`. The conversation is disposable; the session file is the state. Pairs with `vaultmem` (search/registry/router), `vault-recall` (finding what's already written), and `vault-capture` (durable capture). The vault layout, frontmatter fields, status vocabulary, and glyph convention this skill writes are the normative contract in `SCHEMA.md` (run `vaultmem vaults` for the live registry). The templates below are the operational shapes; `SCHEMA.md` is the reference when they disagree. ## Always-on activation The `SessionStart` hook prints a picker line (`vaultmem sessions`) ending in an AGENT DIRECTIVE — the trailing prompt that tells the agent what to do with the picker. Its wording is configurable (the registry's `directive_file`); the default asks the agent to route session handling through this skill. That directive is binding: invoke this skill FIRST, every …
Read the whole file at its exact version.
How to install
mdr add jayantak/vaultmem/session@sha256:2a266ae2d8dbf499The line at the top of this page pins the label git:20260817.76f9246, 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_fzrnorg3zdyizm26)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 24, 2026 and Aug 17, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260817.76f9246 latest | 2026-08-17 | 76f9246 | 23,841 B | A | view · diff |
| git:20260806.9aa5028 | 2026-08-06 | 9aa5028 | 23,221 B | A | view · diff |
| git:20260801.7078e87 | 2026-08-01 | 7078e87 | 22,698 B | A | view · diff |
| git:20260724.ef729e3 | 2026-07-24 | ef729e3 | 19,360 B | A | view · diff |
| git:20260724.b0495fb | 2026-07-24 | b0495fb | 19,316 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 (23841 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_fzrnorg3zdyizm26 GET https://markdownregistry.com/api/v1/resolve?ref=jayantak/vaultmem/session GET https://markdownregistry.com/api/v1/blob/2a266ae2d8dbf499f18a44c55e836751dcec70ef3129a614d661ef6db294f4dc
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 jayantak/vaultmem
Every file in jayantak/vaultmem