What is update-foundation?

A routine for applying Foundation product updates on the machine that runs the vault. It fetches changes, checks the repository state, and restarts the application when appropriate.

Use it to update the code checkout, verify the application’s health, restart it after updates, and report changes to skill files.

It keeps the local product current while checking for risks to stored data and reporting pulls, restarts, failures, or stops.

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/update-foundation/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/update-foundation/github.svg)](https://agentmods.dev/skills/dgraziosi/foundation/update-foundation)

Your own site

<a href="https://agentmods.dev/skills/dgraziosi/foundation/update-foundation"><img src="https://agentmods.dev/badge/skills/dgraziosi/foundation/update-foundation/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/update-foundation"><img src="https://agentmods.dev/badge/skills/dgraziosi/foundation/update-foundation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 625 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.

Model	Per session	Once invoked
Fable 5.1	$0.00035	$0.00625
Opus 5.5	$0.00014	$0.00250
Sonnet 5.5	$0.00007	$0.00125
Haiku 4.5	$0.00003	$0.00063

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

Security

Grade A, and why

update-foundation 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 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.

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.

.agents/skills/update-foundation/SKILL.md · 42 lines

How it starts

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

Update Foundation

You are applying product updates on the machine that runs this vault. The user can run this, or attach it to Vault Keeper.

Call bootstrap only if you need the current tools after the restart.

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.” Life data stays in the vault, not in git.

Schedule and voice

Weekdays, late morning local time. If the clone is already up to date and /health is green, stay quiet. Ping the user when you pulled, restarted, failed, or stopped because a pull would risk stored data. If .agents/skills/ changed, ping Chief of Staff with the changed folder names. Do not stay quiet on a skill-only change.

User config (fill in)

Foundation clone path: (the git checkout that pnpm start uses)
MCP / health base: http://127.0.0.1:8787
FOUNDATION_DATA: (from .env; default ./data)

Steps

Record the current HEAD SHA (git rev-parse HEAD). Do this before fetch or pull. After a pull you may also use ORIG_HEAD.
In the Foundation clone: git fetch origin.
If HEAD is main (or the branch tracking origin/main) and origin/main is ahead, git pull --ff-only. Fast-forward only.
If you pulled: restart the app (pnpm start) so migrations run. No image rebuild. Wait until GET /health returns { ok: true, service: "foundation", db: "up" }. Then diff .agents/skills/ against the SHA you recorded (or ORIG_HEAD). If that tree changed, ping Chief of Staff with the changed folder names. Do not stay quiet on a skill-only change. A harness that points at .agents/skills/ already sees those files. One tree. Do not copy .agents/skills/ into a harness skill library.
If you did not pull and /health is green: stay quiet.

Stop and ping

Working tree is dirty (other than ignored data like FOUNDATION_DATA / .env secrets). Stop and tell the user.
HEAD is not main / not tracking origin/main. Stop and tell the user.
Pull is not a fast-forward, would merge, or would conflict. Stop and tell the user.
The next step would remove FOUNDATION_DATA or delete the data folder.
.env would point the vault at a different leftover cluster.
Health does not come back after the app restart.

Read the full file on GitHub · 42 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 First seen · 42 lines · 35 tokens per session scan A 486325e61e6e

Subscribe to this mod's changes

update-foundation is a skill published in the GitHub repository dgraziosi/foundation (1 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 625 once invoked, about $0.0001 per session on Opus 5.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.

update-foundation next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
update-foundationdgraziosi/foundation	Skill	1	today	MIT	A	35	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