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/agentic-insights/foundry/claude-mdgit clone --depth 1 https://github.com/Agentic-Insights/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/agentic-insights/foundry/claude-md)<a href="https://agentmods.dev/instructions/agentic-insights/foundry/claude-md"><img src="https://agentmods.dev/badge/instructions/agentic-insights/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.00936 | $0.00936 |
| Opus 5 | $0.00468 | $0.00468 |
| Sonnet 5 | $0.00187 | $0.00187 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
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 3d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - Terse Marketplace Guidance
Guidance for Claude Code when working with the Agentic Insights Plugin Marketplace.
Repository Structure
plugins/
├── <plugin-name>/
│ ├── .claude-plugin/plugin.json
│ ├── README.md
│ ├── CHANGELOG.md
│ ├── LICENSE (Apache-2.0)
│ ├── skills/
│ │ └── <skill-name>/SKILL.md (+ references/, assets/, scripts/)
│ ├── agents/
│ │ └── <subagent-name>.md
│ ├── examples/
│ └── recordings/
Plugin Purpose
- Lead generation - Showcase AI engineering expertise
- Client enablement - Post-engagement momentum patterns
- Product-ized solutions - Repeatable consulting encoded as skills
Skill Structure (Agent Skills Spec)
- Required:
SKILL.mdwith YAML frontmatter (name, description) + Markdown instructions - Optional dirs:
scripts/(executable code),references/(detailed docs),assets/(static files) - No other subdirectories allowed
- Keep SKILL.md under 500 lines (use progressive disclosure)
- Directory name MUST match frontmatter
name:field
Frontmatter Fields
- Required:
name(1-64 chars, lowercase alphanumeric-hyphens),description(1-1024 chars, include "Use when...") - Optional:
license(SPDX),compatibility(environment reqs),metadata(author, version, tags),allowed-tools(space-delimited)
Skill Writing Patterns
Terse (Preferred for Action Skills)
- Bullet points, no prose
- "Do this", "Then this"
- Concrete examples only
- Reference detailed docs via links
- ~50-100 lines typical
Comprehensive (For Teaching/Reference)
- Can exceed 500 lines if justified
- Multiple sections with explanations
- Extensive examples embedded
- Use for: tutorials, API docs, specifications
See assets/ subdirectory for style examples.
Quality Checklist
- Validate with
skills-ref validate path/to/skill - SKILL.md exists with valid frontmatter
- Description includes "Use when..."
- Examples are runnable/concrete
- No hardcoded paths (use relative paths)
- Progressive disclosure applied (refs → references/, assets/)
- Cross-platform compatible (test with multiple agents)
- Licensed under Apache-2.0
- Plugin has README.md with installation instructions
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.
- 3d ago First seen · 114 lines · 936 tokens per session scan A 5499fbadf41a
foundry CLAUDE.md is an instructions file published in the GitHub repository Agentic-Insights/foundry (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 936 tokens to every session, about $0.0047 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.