Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add cobibean/agent-memory-wiki --skill obsidian-memory-wikigit clone --depth 1 https://github.com/cobibean/agent-memory-wikiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/cobibean/agent-memory-wiki/obsidian-memory-wiki)<a href="https://agentmods.dev/skills/cobibean/agent-memory-wiki/obsidian-memory-wiki"><img src="https://agentmods.dev/badge/skills/cobibean/agent-memory-wiki/obsidian-memory-wiki.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00038 | $0.03799 |
| Opus 5 | $0.00019 | $0.01899 |
| Sonnet 5 | $0.00008 | $0.00760 |
| Haiku 4.5 | $0.00004 | $0.00380 |
Grade A, and why
obsidian-memory-wiki scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian Memory Wiki
Canonical Package
obsidian-memory-wiki is the canonical parent skill for three formerly separate phases:
obsidian→ low-level vault/file operations.prepforreset→ context-reset and end-of-session handoff capture.wikijanitor→ scheduled or manual memory-wiki reconciliation.
The old skill names may still exist as compatibility slash-command aliases so /prepforreset, /wikijanitor, and /obsidian keep working. New automation, cron wrappers, and shared-skill installs should load/install this parent package:
--skills obsidian-memory-wiki
Do not schedule new runs with --skills wikijanitor,obsidian or --skills prepforreset,obsidian; those names are compatibility aliases and may be absent on newer profiles.
When to Use
Use this skill when:
- Reading, searching, creating, or editing notes in an Obsidian vault.
- The user says “prep for reset”, “prepare for a context window”, or invokes
/prepforreset. - A scheduled or manual wiki janitor should review recent sessions and memory-wiki notes.
- Installing or packaging this workflow for another compatible agent runtime.
Do not use it for:
- Dumping raw transcripts without distillation.
- Storing secrets or credential values in notes.
- Mutating non-wiki memory stores, project repositories, manifests, or backlogs unless the user separately asks for that mutation.
- Writing outside the resolved vault root.
Required Setup and Safety
- Resolve the vault path before file operations.
- Preferred in Hermes: injected skill config
obsidian_memory_wiki.vault_pathfrom the active profileconfig.yaml. - Compatibility fallback for other runtimes:
OBSIDIAN_VAULT_PATHfrom the active process environment. - If neither source provides a concrete path, stop and request configuration; never guess a vault from an ambient directory.
- Preferred in Hermes: injected skill config
- Resolve the final absolute path and refuse writes whose resolved path is outside the vault root.
- Prefer file tools for note operations:
read_file,search_files,write_file, andpatch. - Use terminal only for environment/profile checks, path resolution, or verification that genuinely needs a shell.
- Keep durable knowledge separate from stale task progress. If it will be stale next week, put it in a handoff/session note, not a permanent concept note.
- Never print or store raw secrets. Reference only secret locations such as
.env, keychain, vault item, or config path.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 264 lines · 38 tokens per session scan A 99a295562a71
obsidian-memory-wiki is a skill published in the GitHub repository cobibean/agent-memory-wiki (23 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 3,799 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
personal-api
Turn an Obsidian vault into an AI-readable personal identity layer. Use when setting up ME.md and AGENT.md, scaffolding the full Knowledge Palace v2 structure, onboarding AI assistants, or maintaining the vault contract. Default setup creates the complete 30.knowledge system; --minimal creates only the lightweight…
okf
Author, maintain, and consume Open Knowledge Format (OKF) knowledge bundles — portable markdown + YAML frontmatter that both humans and agents read. Use when capturing project knowledge (services, APIs, schemas, metrics, runbooks, decisions) into an OKF bundle, when updating one after code or docs change, or when a…
rethink
Challenge system assumptions against accumulated evidence. Triages observations and tensions, detects patterns, generates proposals. The scientific method applied to knowledge systems. Triggers on "/rethink", "review observations", "challenge assumptions", "what have I learned".
graph
Interactive knowledge graph analysis. Routes natural language questions to graph scripts, interprets results in domain vocabulary, and suggests concrete actions. Triggers on "/graph", "/graph health", "/graph triangles", "find synthesis opportunities", "graph analysis".
remember
Capture friction as methodology notes. Three modes — explicit description, contextual (review recent corrections), session mining (scan transcripts for patterns). Triggers on "/remember", "/remember [description]".
seed
Add a source file to the processing queue. Checks for duplicates, creates archive folder, moves source from inbox, creates extract task, and updates queue. Triggers on "/seed", "/seed [file]", "queue this for processing".