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 mrDesign-ww/vault-os --skill wiki-querygit clone --depth 1 https://github.com/mrDesign-ww/vault-osWrote 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/mrdesign-ww/vault-os/wiki-query)<a href="https://agentmods.dev/skills/mrdesign-ww/vault-os/wiki-query"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/wiki-query/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/mrdesign-ww/vault-os/wiki-query"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/wiki-query.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.00023 | $0.00377 |
| Opus 5 | $0.00012 | $0.00188 |
| Sonnet 5 | $0.00005 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
wiki-query 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 7d 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
Query canonical memory
Determine the active zone first. Read only its hot cache and index. Run:
/usr/bin/python3 scripts/memory-model.py retrieve "QUERY" --zone ZONE --loadout ROLE
Use designer, builder, researcher, reviewer or general according to the task. Designer, builder and reviewer require --project PROJECT-SLUG. Role budgets are hard caps; --top can only reduce them. Use memory-model.py inspect to see exclusions, selected snippets, candidate inbox state and budget use. Read approved L3, explicit current L2, then relevant L1. Treat legacy-unverified results as discovery candidates that require confirmation. Add --include-l0 only to inspect original evidence.
Automatically inferred or uncertain claims are not answers or canonical memory. If they are worth preserving, propose them through scripts/memory-candidates.py under the shared zone lock. Do not release after file creation: with the same owner token update the candidate catalog, zone log and hot cache, rebuild and validate, create a scoped local Git checkpoint, release in the final path, then run a post-release candidate list or --include-l0 project query. They remain L0 until evidence review and a separate L1 or L2 page is approved.
If retrieval reports a stale or missing index, acquire the shared zone lock, retain its token, run build --zone ZONE --lock-token TOKEN and validate --zone ZONE --lock-token TOKEN, then release in a finally path and retry. An expired lock stays fail-closed until explicit recovery. Never query multiple zones or use another zone's index.
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.
- 7d ago First seen · 17 lines · 23 tokens per session scan A 79e672d7daaa
wiki-query is a skill published in the GitHub repository mrDesign-ww/vault-os (2 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 377 once invoked, about $0.0001 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-09-05.
Other skills, from other repositories
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
mnemos
Task-scoped memory lifecycle — typed MnemoGraph prevents lossy context compaction by treating facts/decisions/code-refs/handoffs as distinct node types with per-type eviction policies.
grimoire
Use when the user says 'update context', 'update claude', 'save library', or after significant project changes.
keep-the-why
Extract and preserve the reasoning code cannot explain - decisions, rejected alternatives, workarounds, incidents, constraints - plus project setup and maintainer interviews. Not for what changed (see Keep a Changelog) - only why. Also the place for complaints, feedback and settings changes about this skill itself.
ln-31-performance-optimizer
Profiles and improves a measured latency, throughput, CPU, memory, or I/O problem. Not for speculative tuning or cosmetic refactoring.