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/automatizatodo/capforge/claude-mdgit clone --depth 1 https://github.com/automatizatodo/capforgeWrote 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/automatizatodo/capforge/claude-md)<a href="https://agentmods.dev/instructions/automatizatodo/capforge/claude-md"><img src="https://agentmods.dev/badge/instructions/automatizatodo/capforge/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.00629 | $0.00629 |
| Opus 5 | $0.00315 | $0.00315 |
| Sonnet 5 | $0.00126 | $0.00126 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
capforge 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 4d 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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CAPforge — project context
Open-source MCP server that makes AI agents (Claude Code, Cursor) get SAP CAP/CDS and UI5 right: modern scaffolding plus a real validation loop (cds compile).
Rules
- Never
git pushwithout explicit user confirmation. - Commit messages: 4-5 words, imperative, no watermarks (no Co-Authored-By / Generated with).
- No comments in generated code; the code explains itself.
- Every tool change is verified before committing:
node --check server.jsplus the tests below. - Files under
knowledge/are anchored to cited official sources — do not add rules without a source, or mark them as own additions (like the migration map). - Examples use generic SAP canonical domains only (bookshop, ACME). Never real-world project data.
Architecture
server.js— the whole MCP server (stdio). Tools:cap_project_context,cap_scaffold_entity,cap_write_files,cap_validate,cap_lint,cap_deploy_check,cap_analyze_legacy_ui5,ui5_scaffold_section,ui5_validate_view,ui5_lint. Resource:conventions://cap(serves knowledge/ + conventions/ combined).knowledge/— canonical core (Free): CAP/UI5 best practices with sources. 01-modeling, 02-services, 03-annotations, 04-data-tooling, 05-migration (own map), 06-ui5.conventions/— house profile, overridable with envCAPFORGE_CONVENTIONS.sandbox/— minimal CAP project for the tests (includesui5app/, the ui5lint testbed).docs/— public website (GitHub Pages from /docs, domain capforge.dev).extension/— VS Code extension that registers the server viamcpServerDefinitionProviders(VS Code 1.101+).build.jsbundles server.js with esbuild intoserver/server.mjsand copies knowledge/conventions;npx vsce packageproduces the .vsix. Settingcapforge.conventionsPath-> envCAPFORGE_CONVENTIONS. No source duplication: the repo root is the single source of truth.- It calls no LLM (BYOK): the value is knowledge plus deterministic validation.
Verify
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.
- 4d ago First seen · 31 lines · 629 tokens per session scan A 9c7e9a37a771
capforge CLAUDE.md is an instructions file published in the GitHub repository automatizatodo/capforge (0 stars, last pushed 25d ago), licensed MIT. It adds 629 tokens to every session, about $0.0031 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
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
abap2UI5 CLAUDE.md
Claude Code instructions for abap2UI5/abap2UI5: All project guidance lives in AGENTS.md — the single source of truth for this repository (architecture and the layered design, the src/00-99 packages, the generated app/webapp mirror, the build and delivery pipeline, the CI gates and ABAP code style).
llm-context.py CLAUDE.md
Instructions for cyberchitta/llm-context.py, covering claude.md, working notes (gitignored) and draining the field notes.
seekstone CLAUDE.md
Claude Code instructions for shaqmughal/seekstone, covering claude.md, what this repo is, commands, the harness itself (run after npm install) and architecture.
cyxj-groksearch CLAUDE.md
Claude Code instructions for chenyuxiaojin/cyxj-groksearch, covering claude.md, 常用命令 and 结构与坑.
Plonk AGENTS.md
AGENTS.md instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.