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 ondrasek/cc-plugins --skill vault-explaingit clone --depth 1 https://github.com/ondrasek/cc-pluginsWrote 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/ondrasek/cc-plugins/vault-explain)<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/vault-explain"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/vault-explain/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/vault-explain"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/vault-explain.svg" alt="Reviewed on agentmods" width="80" 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.00064 | $0.00812 |
| Opus 5.5 | $0.00026 | $0.00325 |
| Sonnet 5.5 | $0.00013 | $0.00162 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
vault-explain 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 1mo 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Explain
Read-only — does not modify any files.
Context Files
skills/shared/references/methodology-framework.md— shared principles, hook architecture, exit codes, 7 quality dimensionsskills/vault-setup/references/methodology.md— vault-specific dimensions, rationale, adaptation rulesskills/vault-setup/references/analysis-checklist.md— how vaults are analyzedskills/vault-setup/references/workflow-catalog.md— GitHub workflow categories and options
Example Questions
"Why validate frontmatter?" -- Dimension 1 (Frontmatter Integrity). YAML frontmatter is the structured backbone of an Obsidian vault. Broken frontmatter causes Dataview queries to fail silently, search to miss notes, and plugins that depend on metadata to malfunction. Validation catches missing required fields, type mismatches, and unparseable dates before they propagate.
"What's gitignored and why?" -- Dimension 7 (Git Hygiene). Obsidian writes volatile state files (workspace.json, workspace-mobile.json) that change on every session, creating constant merge conflicts in shared vaults. Plugin caches and hotkey configs are machine-specific. The methodology excludes these while preserving community plugin configs, snippets, and templates that should be version-controlled.
"How does the quality gate work?" -- Hook Architecture in methodology-framework.md. The quality gate runs as a Stop hook (exit code 2). It checks enabled dimensions sequentially, failing fast at the first error. Claude reads the structured error output and fixes the issue. The gate re-runs automatically until all checks pass. This prevents "lost in the middle" — long error lists cause Claude to skip or half-fix items.
"What GitHub workflows can I set up?" -- See workflow-catalog.md. Categories include: frontmatter validation on push, link checking on PR, spelling on changed .md files, daily note generation, calendar sync, attachment optimization. The setup skill proposes workflows based on vault characteristics and can research anthropics/claude-code-action for AI-powered review workflows.
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.
- 1mo ago First seen · 48 lines · 64 tokens per session scan A 9a0fb8625f57
vault-explain is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 64 tokens to every session and 812 once invoked, about $0.0003 per session on Opus 5.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-31.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.