Borrowing it
Nothing to install: this file belongs to EezyMAcc/mcp-loop-build-demo. 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/EezyMAcc/mcp-loop-build-demo/main/CLAUDE.mdgit clone --depth 1 https://github.com/EezyMAcc/mcp-loop-build-demoWrote 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/eezymacc/mcp-loop-build-demo/claude-md)<a href="https://agentmods.dev/instructions/eezymacc/mcp-loop-build-demo/claude-md"><img src="https://agentmods.dev/badge/instructions/eezymacc/mcp-loop-build-demo/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.01807 | $0.01807 |
| Opus 5 | $0.00903 | $0.00903 |
| Sonnet 5 | $0.00361 | $0.00361 |
| Haiku 4.5 | $0.00181 | $0.00181 |
Grade A, and why
mcp-loop-build-demo 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Operating rules for autonomous work on this repository. Read this fully before touching any code. These rules are non-negotiable and override any instinct to "just make the gate pass."
1. What this project is
A Model Context Protocol (MCP) server that lets an LLM client (e.g. Claude Desktop) browse and curate posts from a hand-picked list of Instagram tattoo artists, via Instagram's Business Discovery API.
Architecture is a clean two-layer split:
core— all real logic: domain models, typed errors, repositories (JSON-file persistence), the Graph API client, image processing, and the services that orchestrate them. Knows nothing about MCP.server— a thin FastMCP adapter that exposescoreas MCP tools. Holds no business logic.
This split exists so a phase-2 GUI can later reuse core directly without
a rewrite. Do not leak MCP concepts into core, and do not put logic in
server.
Full build plan and tool contracts live in PLAN.md. This file governs
how you work; PLAN.md governs what you build.
2. Golden rules (anti-cheat — violating any of these fails the run)
- Never edit, delete, skip, weaken, or
xfaila test to make a gate pass. If a test is wrong, stop and record it inBLOCKERS.md— do not "fix" it by making it assert less. - Never weaken tooling config to pass a gate.
ruff,mypy --strict, and the coverage floor (--cov-fail-under=90) are fixed. Do not editpyproject.tomllint/type/coverage settings to get green. - Never make a live network call in the test path. All HTTP to Instagram is
mocked with
respx. The one real integration test is gated behindRUN_LIVE=1and must never be run by you. - Never commit secrets. No tokens, no IDs, no
.env. Only.env.examplewith placeholder values is committed. - Never weaken coverage by adding blanket
# pragma: no cover. The only permitted pragma is on the stdio entrypointmain()inserver/app.py.
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 · 183 lines · 1,807 tokens per session scan A 4fa98e7ded9f
mcp-loop-build-demo CLAUDE.md is an instructions file published in the GitHub repository EezyMAcc/mcp-loop-build-demo (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,807 tokens to every session, about $0.0090 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
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.
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).
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).
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.
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.