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 Hurricane0698/zot --skill zot-vault-reviewgit 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/skills/hurricane0698/zot/zot-vault-review)<a href="https://agentmods.dev/skills/hurricane0698/zot/zot-vault-review"><img src="https://agentmods.dev/badge/skills/hurricane0698/zot/zot-vault-review/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/hurricane0698/zot/zot-vault-review"><img src="https://agentmods.dev/badge/skills/hurricane0698/zot/zot-vault-review.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.00083 | $0.00467 |
| Opus 5 | $0.00042 | $0.00234 |
| Sonnet 5 | $0.00017 | $0.00093 |
| Haiku 4.5 | $0.00008 | $0.00047 |
Grade A, and why
zot-vault-review 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 11d 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
zot Vault Review
This skill is for periodic maintenance and synthesis of a zot vault.
Use zot-vault-wiki instead when the review turns into a broader compile pass, a feedback-resolution sprint, or a multi-step reorganization across many notes.
Required workflow
- Resolve the vault path from
ZOT_VAULT, then legacyOMEGA_VAULT. - Read
kb/meta/index.md,kb/meta/log.md, andkb/meta/review.mdwhen present. - Run
qmd update -c <vault-local-collection>if note files changed since the last review. - Run
"$ZOT_VAULT/scripts/kb-lint"for a mechanical pass. - Identify orphan notes, stale syntheses, duplicated concepts, and missing active-output drills.
- If the review produced durable insight, file it under
kb/wiki/syntheses/orkb/wiki/queries/. - Use
"$ZOT_VAULT/scripts/kb-smoke-test"when search or CLI wiring looks suspicious. - When the user asks for versioning, review the diff before any commit.
- If the work stops being a review and becomes a structural rewrite, switch to
zot-vault-wiki.
Review outputs to prefer
- weekly synthesis note
- error-pattern note
- "teach it back" drill
- migration suggestions from legacy notes into
kb/wiki/** - retrieval sanity check based on
CLI + qmd smoke test
Guardrails
- Do not auto-commit without checking what changed.
- Keep reviews focused on compounding understanding, not vanity metrics.
- If a file may contain secrets, flag it and recommend rotation or removal.
- Prefer review outputs such as backlog trimming, synthesis notes, and drills over broad note surgery.
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.
- 11d ago First seen · 35 lines · 83 tokens per session scan A 9c07a6683a21
zot-vault-review is a skill published in the GitHub repository Hurricane0698/zot (99 stars, last pushed 4mo ago), licensed MIT. It adds 83 tokens to every session and 467 once invoked, about $0.0004 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
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.