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 burakolgun/vault-anything --skill vault-updategit clone --depth 1 https://github.com/burakolgun/vault-anythingWrote 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/burakolgun/vault-anything/vault-update)<a href="https://agentmods.dev/skills/burakolgun/vault-anything/vault-update"><img src="https://agentmods.dev/badge/skills/burakolgun/vault-anything/vault-update/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/burakolgun/vault-anything/vault-update"><img src="https://agentmods.dev/badge/skills/burakolgun/vault-anything/vault-update.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.00033 | $0.02675 |
| Opus 5 | $0.00016 | $0.01337 |
| Sonnet 5 | $0.00007 | $0.00535 |
| Haiku 4.5 | $0.00003 | $0.00267 |
Grade A, and why
vault-update 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 10d 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/vault-anything:vault-update
Incrementally updates an existing vault. Detects code changes via git diff and static-file changes via SHA256 hash, then re-analyzes and rewrites only the pages that need to change.
Arguments
| Argument | Default | Description |
|---|---|---|
project-dir |
current directory | Project being updated |
--workspace |
<project>/vault-anything/ |
Where existing raw/ and vault/ live |
Phase 0 — Pre-flight
set -e
PLUGIN_ROOT=$(node "$CLAUDE_SKILL_DIR/../vault/resolve-plugin-root.mjs")
WORKSPACE=$(node "$PLUGIN_ROOT/skills/vault/resolve-workspace.mjs" "$@")
PROJECT_DIR=$(echo "$WORKSPACE" | jq -r '.projectDir')
PROJECT_NAME=$(echo "$WORKSPACE" | jq -r '.projectName')
RAW_DIR=$(echo "$WORKSPACE" | jq -r '.rawDir')
VAULT_DIR=$(echo "$WORKSPACE" | jq -r '.vaultDir')
EXISTS=$(echo "$WORKSPACE" | jq -r '.exists')
VAULT_LANG="en" # parse from --lang if provided
If $EXISTS is "false":
- Tell the user:
No vault found. Run /vault-anything:vault <project-dir> first. - STOP.
Set up progress tracking
Before running the phases, use the TaskCreate tool to create the task list:
- Phase 1: Detect changes
- Phase 2: Re-analyze changed code files
- Phase 3: Route new static files
- Phase 4: Regenerate affected pages
- Phase 5: Review and save
Note that phases 2-4 are conditional:
- Phase 2 is skipped if there are no code changes.
- Phase 3 is skipped if there are no new static files in
raw/. - Phase 4 is skipped if no vault pages are affected.
For each skipped phase, mark its task as cancelled (not completed) so the user can see what was skipped.
Mark each running phase in_progress when it starts, completed when it finishes.
Phase 1 — DETECT CHANGES
Mark "Phase 1" as in_progress.
PLAN=$(node "$PLUGIN_ROOT/skills/vault/run-update.mjs" \
"$PROJECT_DIR" "$RAW_DIR" "$PROJECT_NAME")
CODE_CHANGED=$(echo "$PLAN" | jq -r '.codeChanges.hasChanges')
RAW_CHANGED=$(echo "$PLAN" | jq -r '.rawChanges.hasChanges')
FULL_REANALYZE=$(echo "$PLAN" | jq -r '.codeChanges.fullReanalyze')
FULL_GENERATE=$(echo "$PLAN" | jq -r '.requiresFullGenerate')
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.
- 10d ago First seen · 291 lines · 33 tokens per session scan A 65c64957adb4
vault-update is a skill published in the GitHub repository burakolgun/vault-anything (4 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 2,675 once invoked, about $0.0002 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-31.
Other skills, from other repositories
search
Search the gnosis-mcp knowledge base. Keyword (default), hybrid semantic+keyword (--semantic), or git commit history (--git). Includes sanity checks and a reranker warning.
context
Load usage-weighted context from Gnosis MCP. Surfaces most-accessed docs for session startup or topic primers.
ingest
Populate the gnosis-mcp knowledge base — from local files, git history, or a crawled website. Handles the full matrix of flags (--force, --prune, --wipe, --embed, --include-crawled) in one place.
manage
CRUD operations on the knowledge base — add, delete, update metadata. For bulk ingest / re-ingest / prune, use /gnosis:ingest instead. Requires GNOSISMCPWRITABLE=true.
setup
First-time setup wizard for Gnosis MCP. Install, init the database, ingest a docs folder, wire your editor — in that order.
status
Verify gnosis-mcp server connectivity, schema integrity, and corpus health. Use when MCP calls fail, return empty, or return unexpected data.