Borrowing it
Nothing to install: this file belongs to Surferdude-AF/CatalogMCP. 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/Surferdude-AF/CatalogMCP/master/CLAUDE.mdgit clone --depth 1 https://github.com/Surferdude-AF/CatalogMCPWrote 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/surferdude-af/catalogmcp/claude-md)<a href="https://agentmods.dev/instructions/surferdude-af/catalogmcp/claude-md"><img src="https://agentmods.dev/badge/instructions/surferdude-af/catalogmcp/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.01742 | $0.01742 |
| Opus 5 | $0.00871 | $0.00871 |
| Sonnet 5 | $0.00348 | $0.00348 |
| Haiku 4.5 | $0.00174 | $0.00174 |
Grade A, and why
CatalogMCP 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CatalogMCP
What this is
A spike demonstrating that MCP (Model Context Protocol) is a good fit for maintaining a product catalog — an MCP server that lets an agent safely mutate a configuration surface (attributes, rules, product data), not just read one.
What we're trying to prove
Setting up a digital product catalog today is either slow (click through a UI for every attribute and rule) or expensive (script it against an API, which turns labor cost into engineering cost for every future change). The claim: an agent talking to a governed MCP tool surface can replace both — "describe what you want in plain language, agent executes it" — without sacrificing safety, because the governance layer (preview, audit, confirm) is what makes ungoverned write access tolerable in the first place.
The guardrails are not a bolt-on feature; they're the precondition for the pitch. A demo that shows mutation without also showing preview/audit/confirm hasn't proven anything.
Status
Implementation complete: domain model, full tool surface (schema + content +
governance), and the 6-step demo script are all built and tested (npm test), and
the demo has been run live against the real Anthropic API — see
demo/transcript.txt and the recorded video linked from the
README. What follows below is retained as the design record (decisions, scope, and
the explicit non-goals) rather than a live TODO list.
Decisions made during discovery:
- Terminal-only, no product UI. The "no UI" scope cut stands. But browsing the catalog is a first-class use case in its own right, not just a demo verification step — the belief is that agents are becoming a primary consumer of catalog data, so an agent reading the catalog back (not a human refreshing a browser) is itself part of the pitch.
- Schema AND content, not schema alone. Schema-only (defining attributes/rules) makes for a poor demo — the compelling story is content setup (loading actual products and their attribute values) validated against schema (required attributes, rules), which is what produces real dry-run previews and real back-and-forth.
- Destructive demo step: after initial setup, delete one product attribute — this is where the two-phase confirm / blast-radius disclosure gets shown (an attribute with live product data behind it is a much more meaningful "are you sure" than deleting an unused one).
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 · 128 lines · 1,742 tokens per session scan A 463c93fe1bd8
CatalogMCP CLAUDE.md is an instructions file published in the GitHub repository Surferdude-AF/CatalogMCP (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,742 tokens to every session, about $0.0087 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.