Borrowing it
Nothing to install: this file belongs to lbruton/claude-context. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lbruton/claude-context/master/.agents/skills/setup-foundation-context/SKILL.mdgit clone --depth 1 https://github.com/lbruton/claude-contextWrote 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/lbruton/claude-context/setup-foundation-context)<a href="https://agentmods.dev/skills/lbruton/claude-context/setup-foundation-context"><img src="https://agentmods.dev/badge/skills/lbruton/claude-context/setup-foundation-context/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/lbruton/claude-context/setup-foundation-context"><img src="https://agentmods.dev/badge/skills/lbruton/claude-context/setup-foundation-context.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.00157 | $0.02480 |
| Opus 5.5 | $0.00063 | $0.00992 |
| Sonnet 5.5 | $0.00031 | $0.00496 |
| Haiku 4.5 | $0.00016 | $0.00248 |
Grade B, and why
setup-foundation-context scanned grade B 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/project.json 2>/dev/null # -> name How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Foundation Context
Onboards a project's agent-facing foundation docs into in-repo .context/, so they travel
with the code and worktrees and are never silently skipped by a sandboxed out-of-repo read
(the DEVS-37 rationale). This is a one-time migration per project — once .context/ is the
canonical home, ongoing upkeep is /context-drift's job, not this skill's.
The baseline doc set
The floor is 5 docs; a project may have more. Migrate/scaffold these 5 into .context/:
.context/ file |
What it holds |
|---|---|
infrastructure.md |
hosting, deploy, ports, services, env, external systems |
architecture.md |
components, data flow, module boundaries, key abstractions |
coding-standards.md |
language/style conventions, lint gates, test conventions |
design-philosophy.md |
product/UX principles, the "why" behind decisions |
reusable-patterns.md |
recurring code patterns, helpers, idioms to reach for |
Project extras are preserved, not forced into the 5. Files like git-topology.md,
implementation-gotchas.md, review-and-ci.md, integrations.md, spec-conventions.md,
and GLOSSARY.md stay as their own .context/ files. The 5 is a minimum, not a cap.
Arguments
[project]— project name (e.g.Forge). Auto-detected from.claude/project.jsonif omitted.--apply— perform the migration. Default is dry-run (plan only, no writes).--doc <name>— limit to one baseline doc (e.g.--doc infrastructure.md).
Phase 0: Project discovery
cat .claude/project.json 2>/dev/null # -> name
Resolve paths:
- Repo root: current working directory (the project repo).
- Project vault:
$(vault-path project), i.e.<repo>/DocVault/(exit 2 = not scaffolded yet; Phase 3 step 0 creates it) - Archived Foundation dir (case a source):
$(vault-path archive)/Projects/{name}/Foundation/. After DEVS-78 these originals only exist in the frozen central repo; they stay there.
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.
- 5d ago Changed df349a15fed5
- 9d ago Changed cbedc53b4cdc
- 11d ago First seen · 198 lines · 157 tokens per session scan B 1af1d1ccbf6b
setup-foundation-context is a skill published in the GitHub repository lbruton/claude-context (2 stars, last pushed 5d ago), licensed MIT. It adds 157 tokens to every session and 2,480 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-17.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…