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-auditgit 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-audit)<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/vault-audit"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/vault-audit/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-audit"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/vault-audit.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.00061 | $0.00816 |
| Opus 5.5 | $0.00024 | $0.00326 |
| Sonnet 5.5 | $0.00012 | $0.00163 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
vault-audit 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Audit
Read-only — does not modify any files.
Context Files
Read these files before starting:
skills/shared/references/methodology-framework.md— shared principles, hook architecture, exit codes, 7 quality dimensionsskills/vault-setup/references/methodology.md— vault-specific 7 dimensions, thresholds, tool research guidanceskills/vault-setup/references/analysis-checklist.md— what to check in the target vault
Workflow
Follow the 5-step audit pattern below. Vault-specific details for each step:
1. Analyze Current State
Detect vault structure: folder hierarchy, .obsidian/ contents, community plugins, daily notes configuration, frontmatter conventions, template files, tag inventory. Inventory existing tool configurations: linter configs, spelling dictionaries, .gitignore coverage, hook scripts, CI workflows.
2. Compare Against Methodology
Check each of the 7 dimensions — see methodology-framework.md for roles and the vault-specific methodology.md for tools and thresholds:
- Frontmatter Integrity — Is YAML frontmatter validated? Required fields defined? Date format enforced?
- Link Integrity — Are broken wikilinks detected? Orphaned notes identified? Missing attachments flagged?
- Naming Conventions — Is a naming pattern enforced? Folder hierarchy consistent? Special characters detected?
- Template Compliance — Are notes validated against declared templates? Required sections checked?
- Tag Hygiene — Is tag taxonomy enforced? Orphan tags detected? Near-duplicates flagged?
- Documentation Quality — Is spelling checked? Prose style consistent? Readability measured?
- Git Hygiene — Is
.gitignorecovering volatile.obsidian/files? Large binaries detected? Merge-conflict-prone files excluded?
3. Check Hook Coverage
Expected hooks:
- SessionStart → vault detection, git hygiene warnings (non-blocking)
- PostToolUse (Edit|Write) → frontmatter validation, spelling (exit 2)
- Stop → quality gate (all enabled dimensions, exit 2)
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 · 89 lines · 61 tokens per session scan A fcfefdf86d65
vault-audit is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 816 once invoked, about $0.0002 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.