Borrowing it
Nothing to install: this file belongs to sixees/mcp-curl. 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/sixees/mcp-curl/main/CLAUDE.mdgit clone --depth 1 https://github.com/sixees/mcp-curlWrote 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/sixees/mcp-curl/claude-md)<a href="https://agentmods.dev/instructions/sixees/mcp-curl/claude-md"><img src="https://agentmods.dev/badge/instructions/sixees/mcp-curl/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/sixees/mcp-curl/claude-md"><img src="https://agentmods.dev/badge/instructions/sixees/mcp-curl/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.01062 | $0.01062 |
| Opus 5.5 | $0.00425 | $0.00425 |
| Sonnet 5.5 | $0.00212 | $0.00212 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
mcp-curl 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code (claude.ai/code) when working in this repository.
This file says how to work here, and nothing else. Three companion documents own the rest, and each fact lives in exactly one of them:
| Question | Document |
|---|---|
| What must a change not break? (numbered invariants, trust boundaries) | ARCHITECTURE.md |
| How is this system built? (stack, lifecycle, security detail) | docs/architecture/architecture.md |
| What must the work look like? | CONVENTIONS.md |
| What went wrong before, and what did it teach us? | LESSONS.md |
| How is the workflow configured for this repo? | docs/compound/compound-engineering-profile.md |
Session rules under .claude/rules/ load automatically. They are gitignored and
per-clone — run /sixees-workflow:init-compound in a fresh clone to get them.
This document is read at the start of every session, and that is the whole
mechanism. Nothing here is checked by anything. Keep it short enough to be read:
a CLAUDE.md nobody reaches the end of governs only its first half.
This guidance is offered forward; your answers never are.
/sixees-workflow:refresh-compound reports what the current scaffold carries that
this copy lacks — the paragraphs saying what this document owns and how to keep it —
and inserts only what you authorise. It writes no answer and removes no line.
/sixees-workflow:reconcile-standards is the other pass: it moves prose that belongs
in a sibling into that sibling, moves prose that belongs here in from one, and reconciles this file's section names against the
shipped scaffold's — never against the sections already in this copy, which are the
thing being measured. Both ask before writing, and neither commits.
Keep this paragraph outside the blockquote above, which you are told to delete once
the document is filled.
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 Changed · +28 tokens per session a79b7c4a19f8
- 6d ago Changed · +15 lines · +230 tokens per session 3b3b9556f158
- 1mo ago Changed · -48 lines · -1,674 tokens per session 5258e5160fe9
- 1mo ago First seen · 115 lines · 2,478 tokens per session scan A bd64c1e1c0dc
mcp-curl CLAUDE.md is an instructions file published in the GitHub repository sixees/mcp-curl (4 stars, last pushed yesterday), licensed MIT. It adds 1,062 tokens to every session, about $0.0042 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.