What is vault-health?

A weekday written check of a running Foundation vault, which is a local instance of the Foundation product and its stored data. It checks more than whether the health endpoint responds.

Use it to check the local service, data location, database state, and other configured health conditions, then report failures to the user.

It helps identify when the local vault is not running correctly or is using the wrong data folder, while staying quiet when everything is healthy.

How dgraziosi/foundation configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to dgraziosi/foundation. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/dgraziosi/foundation/main/.agents/skills/vault-health/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/dgraziosi/foundation

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/dgraziosi/foundation/vault-health/github.svg)](https://agentmods.dev/skills/dgraziosi/foundation/vault-health)

Your own site

<a href="https://agentmods.dev/skills/dgraziosi/foundation/vault-health"><img src="https://agentmods.dev/badge/skills/dgraziosi/foundation/vault-health/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/dgraziosi/foundation/vault-health"><img src="https://agentmods.dev/badge/skills/dgraziosi/foundation/vault-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 686 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00052	$0.00686
Opus 5.5	$0.00021	$0.00274
Sonnet 5.5	$0.00010	$0.00137
Haiku 4.5	$0.00005	$0.00069

Measured 2mo ago against content hash 39838947101a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vault-health scanned grade A with 1 finding 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 2mo 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

You are not the host script. Do not start Postgres or the app. Do not install a schedule. Do not wake a bot to curl /health on a timer. That job is [`scripts/keep-vault-up.sh`](../../../scripts/keep-vault-up.sh). It star

.agents/skills/vault-health/SKILL.md · 40 lines

How it starts

The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Vault health

You are writing the weekday vault-health report. The user can run this, or attach it to Vault Keeper.

Read docs/VAULT_HEALTH.md and follow the written-report section. Call bootstrap if you need the current tools.

You are not the host script. Do not start Postgres or the app. Do not install a schedule. Do not wake a bot to curl /health on a timer. That job is scripts/keep-vault-up.sh. It starts the two host programs, curls /health, and fails on an empty cluster next to a real one. First-day 0 user records is healthy. /health green is not enough.

The user is the human who runs this vault on this machine. A vault is this running instance (FOUNDATION_DATA + Postgres). Do not call the graph “the Vault.”

Schedule and voice

Weekdays, 9:15 user-local. If every check passes, stay quiet. Ping the user only on failure.

Keeping the vault up is the host script on this machine’s own schedule. Not this pass. Quiet when health is green and the live folder is the intended real cluster.

User config (fill in; blank means skip that check)

MCP / health base: http://127.0.0.1:8787
FOUNDATION_DATA: (from .env; default ./data) — this path is the vault
Well-known node ids or titles: (optional; skip if unset)
Backup path: BACKUP_ROOT (default: sibling of the data dir; skip only if the user unset it)
Backup stale after: 48 hours (only if BACKUP_ROOT is set)

Checks (in order)

GET /health — HTTP 200 and { ok: true, service: "foundation", db: "up" }. If this fails, ping. Do not start the host programs.
FOUNDATION_DATA is the real vault: not an agent profile or memory directory, and not an empty leftover Postgres cluster (missing/empty postgres dir, no PG_VERSION, host cannot read PG_VERSION, empty live next to a backup or second tree that has people). Do not mkdir the live path on that miss. A first-day vault with seed types and 0 user records is healthy unless well-known nodes were configured.
If well-known nodes are configured, get/search them and confirm they exist (not soft-deleted). If none configured, skip.
Backup path defaults to BACKUP_ROOT. Skip only if the user unset it. If set, the path is present and the newest artifact is newer than 48 hours. Newest artifact may be foundation-YYYYMMDD.sql.age. Health checks; it does not dump. Nag if the dump is missing or old.

Read the full file on GitHub · 40 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.

2mo ago Changed 39838947101a
2mo ago First seen · 40 lines · 52 tokens per session scan A 6c5d12417bc7

Subscribe to this mod's changes

vault-health is a skill published in the GitHub repository dgraziosi/foundation (1 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 686 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

DevOps and cloud

vault-health next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
vault-healthdgraziosi/foundation	Skill	1	today	MIT	A	52	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	today	MIT	A	103	Claude Code

foundation: Skill for Claude Code