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 agentmods add commands/hurricane0698/zot/vault-wikigit clone --depth 1 https://github.com/Hurricane0698/zotWrote 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/commands/hurricane0698/zot/vault-wiki)<a href="https://agentmods.dev/commands/hurricane0698/zot/vault-wiki"><img src="https://agentmods.dev/badge/commands/hurricane0698/zot/vault-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.00000 | $0.00234 |
| Opus 5 | $0.00000 | $0.00117 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
vault-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 6d 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
Maintain the current zot vault as a compiled wiki.
Arguments: $ARGUMENTS
Workflow:
- Resolve the vault path from
ZOT_VAULT, then legacyOMEGA_VAULT. - Read
AGENTS.md,kb/meta/index.md,kb/meta/log.md, andkb/meta/review.md. - Choose the matching operation:
compile,ingest,query,lint, orfeedback. - Keep
kb/raw/**immutable and write durable synthesis tokb/wiki/**. - Update
kb/meta/index.mdafter meaningful navigation changes and append tokb/meta/log.md. - Leave an active-output drill after meaningful ingest or synthesis unless the user explicitly declines.
- If open feedback exists under
kb/human/feedback/open/**, resolve it before large restructures when practical.
If $ARGUMENTS names an operation or target area, use it to scope the pass.
Use this command when the job crosses skill boundaries, such as:
- ingest plus restructure
- query plus promotion
- review plus feedback resolution
- lint plus broad wiki cleanup
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.
- 6d ago First seen · 21 lines · 0 tokens per session scan A 0602b20b27d9
vault-wiki is a command published in the GitHub repository Hurricane0698/zot (99 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 234 tokens. 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 commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.