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 sandsower/memento-vault --skill inceptiongit clone --depth 1 https://github.com/sandsower/memento-vaultWrote 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/sandsower/memento-vault/inception)<a href="https://agentmods.dev/skills/sandsower/memento-vault/inception"><img src="https://agentmods.dev/badge/skills/sandsower/memento-vault/inception.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.00035 | $0.00274 |
| Opus 5 | $0.00017 | $0.00137 |
| Sonnet 5 | $0.00007 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
inception 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.
What it actually says
Inception
Run Memento Vault consolidation to find patterns across notes.
Process
-
Determine mode:
- Default: incremental run
- Dry run: user says preview, dry run, or what would be found
- Full run: user says full, all notes, rescan, or backfill
-
Prefer the installed local script when available:
python3 ~/.claude/hooks/memento-inception.py --verbose [--dry-run] [--full]
-
If the script is unavailable, explain that Inception requires a local Memento install with the consolidation hook.
-
Interpret common outcomes:
- Lock held: another run is active
- Missing dependencies: install
numpy hdbscan scikit-learn - No embeddings: reindex and embed the vault
- Config error: inspect
memento.yml
-
Report clusters found, notes written, and whether it was a dry run.
Rules
- Do not write pattern notes during dry runs.
- Do not hide dependency or indexing failures.
- If pattern notes are written, suggest reviewing the new notes.
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 · 38 lines · 35 tokens per session scan A 86157296ef99
inception is a skill published in the GitHub repository sandsower/memento-vault (12 stars, last pushed 25d ago), licensed MIT. It adds 35 tokens to every session and 274 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
garden-tending
Tend the knowledge garden — diagnose vault health, condense project memos into project.md overviews, create/merge cross-project topics, fix broken links, archive superseded notes, extend trails. Trigger on "tend the garden", "condense", "update project overview", "check vault health", "where are we with X?", "what…
curator-practice
Operating philosophy for autonomous memex curator tending — orientation protocol, signal triage, bounded work units, initiative thresholds, logging conventions. Trigger on cron-launched runs with no user prompt, "use your judgment", "tend without instructions", "do a pass on the vault", "I'll be away — do what needs…
recall
Retrieve session memory across 4 modes — TEMPORAL (date browsing), KEYWORD (FTS lookup), DEEP (cross-session synthesis), LOAD (specific file). Trigger on "what did I do yesterday/last week", "why did we...", "remind me...", "find the memo about...", "last time we...", "patterns across projects", "load the X topic". Do…
memo-writing
How to write effective session memos — format, frontmatter schema, observation extraction, topic-signal append. Trigger on /memex:save, "save this for later", "remember this", "save what we discussed", "document this session", "create a memo", or when the [memex] activity nudge appears in context. Do NOT trigger for…
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
save
Save a user-selected answer, decision, insight, or session summary into an Obsidian vault as one reviewed transaction. Use only when the user explicitly asks to preserve specific conversation content, not when they supply a file or URL to ingest. Triggers: /save, save this, save that answer, file this conversation…