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.
npx agentmods add instructions/xobotyi/cc-foundry/claude-mdgit clone --depth 1 https://github.com/xobotyi/cc-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/xobotyi/cc-foundry/claude-md)<a href="https://agentmods.dev/instructions/xobotyi/cc-foundry/claude-md"><img src="https://agentmods.dev/badge/instructions/xobotyi/cc-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 | $0.01438 | $0.01438 |
| Opus 5 | $0.00719 | $0.00719 |
| Sonnet 5 | $0.00288 | $0.00288 |
| Haiku 4.5 | $0.00144 | $0.00144 |
Grade A, and why
cc-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 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.
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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cc-foundry
Claude Code plugin development repository. Contains plugins that extend Claude Code with domain-specific skills, output styles, hooks, and workflow automation.
Plugins
plugins/ai-helpers/— AI artifact engineering (prompts, skills, agents, styles)plugins/git-commit/— structured commit workflow with validationplugins/skill-enforcer/— skill activation enforcement via lifecycle hooksplugins/the-blueprint/— planning pipeline: DRAFT (discovery → research → alignment → frame → tasks)plugins/the-coder/— language-agnostic coding disciplineplugins/the-statusline/— session metrics status lineplugins/the-writer/— prose discipline for agent-authored textplugins/infrastructure/— infrastructure discipline (Ansible, Docker, Proxmox, Unraid, networking)plugins/the-workflow/— agentic workflow mechanics (CLAUDE.md quality, context handoff)plugins/frontend/— frontend platform disciplineplugins/backend/— backend platform discipline (observability, Prometheus, StatsD, OTel)plugins/grafana/— Grafana platform (dashboards, PromQL, MetricsQL, LogsQL, alerting, provisioning, dataviz)plugins/cli/— CLI platform discipline (CLI design, shell scripting)plugins/open-source/— open-source contribution discipline (issues, pull requests)plugins/golang/,plugins/javascript/,plugins/php/,plugins/python/,plugins/rust/— language disciplinesplugins/wall-clock/— wall-clock and elapsed-time grounding for agent context (hook-only)
Each plugin has its own CLAUDE.md with plugin-specific context.
Creating a New Skill
Full workflow: .claude/guides/skill-creation-workflow.md — 4-phase
process (Research → Scaffold → Write → Ship).
Conventions
Formatting:
- The repo uses Prettier for markdown formatting (
.prettierrc.yamlat root) - After editing any
.mdfile, runyarn dlx prettier --write <file>before committing - Never pass
--parser— the config assigns mdx to CLAUDE.md and files underskills/, markdown to README.md
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 First seen · 115 lines · 1,438 tokens per session scan A b4505344068f
cc-foundry CLAUDE.md is an instructions file published in the GitHub repository xobotyi/cc-foundry (20 stars, last pushed 2d ago), licensed MIT. It adds 1,438 tokens to every session, about $0.0072 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-30.
Other instructions, from other repositories
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.
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).
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.
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).