Borrowing it
Nothing to install: this file belongs to adamgalmor/yamcp. 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/adamgalmor/yamcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/adamgalmor/yamcpWrote 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/adamgalmor/yamcp/claude-md)<a href="https://agentmods.dev/instructions/adamgalmor/yamcp/claude-md"><img src="https://agentmods.dev/badge/instructions/adamgalmor/yamcp/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.00214 | $0.00214 |
| Opus 5 | $0.00107 | $0.00107 |
| Sonnet 5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
yamcp 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.
What it actually says
yamcp
OpenAPI → secure MCP server (scoped auth, allow/deny policy, rate limiting, redacted audit log). See README.md for the request pipeline and architecture.
Verification loop (run before reporting any change done)
npm run build # tsc
npm run lint # eslint src test
npx prettier --check .
npm test # vitest run
This is the same gate CI runs (.github/workflows/ci.yml). All four must pass before a change is considered finished — don't hand back a diff you haven't run this against.
Conventions
- Tests live in
test/*.test.ts(vitest), fixtures intest/fixtures. - Source is organized by pipeline stage:
src/spec(OpenAPI parsing),src/security(auth/policy/rate-limit),src/proxy,src/audit,src/server,src/config. - Format with
npm run format(prettier) rather than hand-formatting.
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 · 21 lines · 214 tokens per session scan A 912c5b2c99fe
yamcp CLAUDE.md is an instructions file published in the GitHub repository adamgalmor/yamcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 214 tokens to every session, about $0.0011 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.