vault-update

vault-update is a skill for Claude Code from burakolgun/vault-anything. It costs 33 tokens per session (2,675 once invoked), scanned A, original, MIT.

An update process for a project knowledge vault, meaning a collection of analysed project pages. It checks code and static-file changes, then rewrites only the pages affected by those changes.

In plain words
What is it for?
Use it to refresh an existing vault after code or static files change, using Git differences and SHA256 file checks to find affected pages.
Why use it?
Reanalysing an entire project after every edit takes time and can create unnecessary changes. This process narrows the update to content that may be out of date.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents.

Part of the vault-anything plugin — 2 skills, 2 agents shipped together

Good fit Use it to refresh an existing vault after code or static files change, using Git differences and SHA256 file checks to find affected pages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/burakolgun/vault-anything/vault-update
Install

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.

Any agent
npx skills add burakolgun/vault-anything --skill vault-update
Clone the repo
git clone --depth 1 https://github.com/burakolgun/vault-anything

Made for: Claude Code.

Or install vault-anything, the plugin that ships this one along with the rest of its 2 skills, 2 agents.

Wrote 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.

agentmods badge for vault-update

README.md
[![agentmods](https://agentmods.dev/badge/skills/burakolgun/vault-anything/vault-update/github.svg)](https://agentmods.dev/skills/burakolgun/vault-anything/vault-update)
Your own site
<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.

agentmods 80×15 button for vault-update

Your own site · 80×15
<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>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,675 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 10d ago against content hash 65c64957adb4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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.

skills/vault-update/SKILL.md · 291 lines

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:

  1. Phase 1: Detect changes
  2. Phase 2: Re-analyze changed code files
  3. Phase 3: Route new static files
  4. Phase 4: Regenerate affected pages
  5. 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')

Read the full file on GitHub · 291 lines

Changes

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.

  1. 10d ago First seen · 291 lines · 33 tokens per session scan A 65c64957adb4

Subscribe to this mod's changes

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.