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-ingestgit 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-ingest)<a href="https://agentmods.dev/skills/mrdesign-ww/vault-os/wiki-ingest"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/wiki-ingest/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-ingest"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/wiki-ingest.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-ingest 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
Ingest into canonical memory
- Determine the active zone and project. Do not inspect another zone.
- Acquire
bash scripts/wiki-lock.sh acquire .vault-meta/write/ZONE --ttl 3600. Save, ingest and evolution share this exact zone lock. Retain the token. After every long phase and before later writes, build and checkpoint, runrenewthencheck. Release in afinallypath on success or failure; never reacquire over expired partial work. - Copy the original source without rewriting it. Project evidence goes in the project's
sources/. Non-project work evidence goes towiki/resources/incoming/; personal and Client non-project evidence goes to that zone'sinbox. Evidence is always L0, regardless of its frontmatter. - Verify the copied bytes or hash. Create a separate L1 page with
memory_provenance, or L2 synthesis when the source clearly changes canonical project state. If the claim is inferred, conflicting or uncertain, create an L0 memory candidate instead and wait for review. - Update project and zone indexes, append-only log, then hot cache.
- Run zone
scan, check the token,build --zone ZONE --lock-token TOKEN, andvalidate --zone ZONE --lock-token TOKEN. Check again, create a scoped local Git checkpoint and never push. - Release in the
finallypath, then run a relevant retrieval query and inspect its current-state snippet. Do not call the plugin repository'swiki-mode.py.
Stop, release the token, and report the exact failure if provenance, zone, source immutability, validation, checkpoint, or retrieval acceptance cannot be established.
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 960f4e9bbe71
wiki-ingest 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.