Borrowing it
Nothing to install: this file belongs to vinsonconsulting/claude-skill-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/vinsonconsulting/claude-skill-foundry/main/CLAUDE.mdgit clone --depth 1 https://github.com/vinsonconsulting/claude-skill-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/vinsonconsulting/claude-skill-foundry/claude-md)<a href="https://agentmods.dev/instructions/vinsonconsulting/claude-skill-foundry/claude-md"><img src="https://agentmods.dev/badge/instructions/vinsonconsulting/claude-skill-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.00790 | $0.00790 |
| Opus 5 | $0.00395 | $0.00395 |
| Sonnet 5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
claude-skill-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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This repo is a library of Claude skills. Each skill is a self-contained folder
under skills/<category>/<name>/ holding a SKILL.md plus any scripts/,
references/, or assets/ it needs. The goal is skills that trigger reliably and
are portable: clone the repo, copy a folder, and it works anywhere Claude reads
skills.
How a skill loads (progressive disclosure)
Claude reads skills in three tiers, cheap to expensive. Author with this in mind:
- Metadata (always loaded): the
nameanddescriptionfrom every skill's frontmatter. This is the only thing Claude sees by default, so the description is what decides whether the skill fires. Keep it dense with triggers. - Body (loaded when the skill fires): the Markdown in
SKILL.md. Keep it under ~500 lines. It's instructions for Claude, not documentation for humans. - Bundled files (loaded on demand):
references/,scripts/,assets/. Push anything long, rarely needed, or reference-like out of the body into these.
The description is the trigger
Under-triggering is the dominant failure mode: Claude tends not to invoke a skill
that would have helped. So the description must state, concretely, when to
use the skill, in the third person, with the words a user would actually use. Lead
with the trigger conditions, then what it does. Be a little pushy. "Use when the
user wants to X, mentions Y, or is working with Z" beats "A skill for X."
Authoring conventions
- One concern per skill. If a SKILL.md sprouts a second job, split it.
- Write the body as imperative instructions to Claude. Explain why a step matters rather than shouting MUSTs; Claude follows reasoning better than emphasis.
- Keep the body lean; move detail to
references/. Bundle ascripts/helper when the same deterministic step recurs, so Claude doesn't re-derive it each time. skills/<category>/<name>/SKILL.mdis the path contract. Frontmatter needsname(matching the folder) anddescription.- Folders under
skills/that start with_(like_TEMPLATE) are ignored by the tooling. - No secrets in any skill. Reference where they live instead.
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 · 57 lines · 790 tokens per session scan A 85ec1be1387d
claude-skill-foundry CLAUDE.md is an instructions file published in the GitHub repository vinsonconsulting/claude-skill-foundry (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 790 tokens to every session, about $0.0040 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.