Borrowing it
Nothing to install: this file belongs to tomershahar/team-foundry. 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/tomershahar/team-foundry/main/CLAUDE.mdgit clone --depth 1 https://github.com/tomershahar/team-foundryWrote 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/instructions/tomershahar/team-foundry/claude-md)<a href="https://agentmods.dev/instructions/tomershahar/team-foundry/claude-md"><img src="https://agentmods.dev/badge/instructions/tomershahar/team-foundry/claude-md.svg" alt="Measured on agentmods" 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.00577 | $0.00577 |
| Opus 5 | $0.00289 | $0.00289 |
| Sonnet 5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
team-foundry CLAUDE.md 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 7d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
team-foundry is an open-source Node CLI (npx create-team-foundry) that helps product
teams articulate outcomes, customers, decisions, and quality bars into repository files.
Tools receive that context through native AGENTS.md support or generated adapters. It's
a culture artifact first, AI context second.
Status
v3.6.0 is published to npm. PROGRESS.md records current work and feature_list.json tracks verification state.
Implemented: manifest-driven scaffolding, solo/full/federated layouts, multi-tool pointers, project identity extraction, safe merge/replace/skip behavior, adopt and migrate flows, playground, drift status and CI gate, Claude Code skills, and prefilled feedback.
Architecture
- Node CLI - entry point is
npx create-team-foundry; command routing lives insrc/index.ts. - Profiles - solo (7-17 files), full flat (23-33), and Claude-capable federated (36-39). Profile and tool selection control which files are materialized on disk.
- Tools - Claude Code, Gemini CLI, Cursor, GitHub Copilot, AGENTS.md-native tools, combined selections, and all tools.
- Manifest -
src/manifest.tsis the source of truth for generated and status-tracked files. - No backend - zero hosted services, API keys, or token costs. Everything runs on the user's own AI tool.
- Coach system - instructions embedded in
.team-foundry/coach.md, not a separate runtime. Root instruction file is kept minimal; full coach playbook loaded on demand. - File frontmatter - every generated file has YAML frontmatter with
purpose,read_when,last_updated,owner.
Key Design Decisions
- Files are structured to make gaps visible, not hide them (mirror, not template pack)
- Coach is diagnostic-first: names the gap before suggesting a fix
- No silent writes - user always confirms before files are modified
- Root instruction file is kept minimal; full coach playbook loaded on demand
AGENTS.mdis the shared routing map; tool-specific files point to it- Claude skills are generated and advertised only when the selected tool set includes Claude Code
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.
- 7d ago First seen · 43 lines · 577 tokens per session scan A e70786816903
team-foundry CLAUDE.md is an instructions file published in the GitHub repository tomershahar/team-foundry (1 stars, last pushed 1mo ago), licensed MIT. It adds 577 tokens to every session, about $0.0029 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.