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/ai-alexbaum/ip-mcp/claude-mdgit clone --depth 1 https://github.com/AI-AlexBaum/IP-MCPWrote 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/ai-alexbaum/ip-mcp/claude-md)<a href="https://agentmods.dev/instructions/ai-alexbaum/ip-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ai-alexbaum/ip-mcp/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.01734 | $0.01734 |
| Opus 5 | $0.00867 | $0.00867 |
| Sonnet 5 | $0.00347 | $0.00347 |
| Haiku 4.5 | $0.00173 | $0.00173 |
Grade A, and why
IP-MCP 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 5d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this is
An MCP server for trademark and company research over public registers. One file, zero dependencies, Node 18+, ESM. It speaks MCP over stdio with a hand-rolled JSON-RPC loop — there is no SDK, no build step and no bundler.
Distribution is npx -y github:AI-AlexBaum/IP-MCP, straight from the repo. Nothing is
published to npm, so package.json's bin and files must stay correct or the install
path silently breaks.
Commands
npm run smoke # the entire test suite (24 checks, hits live registers)
node --check src/index.js # syntax gate
node src/index.js # speaks MCP on stdin/stdout
To run a single check, pipe one JSON-RPC line in — this is the fastest way to iterate on a tool:
printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"tm_clearance","arguments":{"name":"Northwind"}}}' \
| node src/index.js
The paid tools need credentials in the environment, never in the repo:
COMPANYINFO_USERNAME=… COMPANYINFO_PASSWORD=… node src/index.js
The smoke test calls live third-party APIs. A failure can mean upstream drift rather
than a regression — check the endpoint by hand before assuming the code broke. The four
paid nl_company_* tools are deliberately not in the suite: each run would cost money
and return real company data. Verify those by hand when you touch them.
Architecture
src/index.js is layered top to bottom:
- Constants —
OFFICES(register codes),LIVE(which statuses count as a live right),VIES_MS(VAT member states). http()— every outbound call goes through it. Three retries with backoff, 90s timeout, throws on non-2xx. It never converts a failure into an empty result.- Source adapters, one group per data source: TMview + EUIPO
copla(trademarks), GLEIF + VIES (companies),EU_REGISTERS(sixteen national registers), and the Company.info SOAP layer (paid, Dutch Handelsregister). TOOLS— JSON schemas — andHANDLERS— name → function.- stdio loop — line-buffered reader plus
dispatch(), which tracks in-flight requests so a client closing stdin mid-call does not drop pending replies.
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.
- 5d ago First seen · 140 lines · 1,734 tokens per session scan A 42c9226fb2c6
IP-MCP CLAUDE.md is an instructions file published in the GitHub repository AI-AlexBaum/IP-MCP (0 stars, last pushed 8d ago), licensed MIT. It adds 1,734 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
ZATCA AGENTS.md
AGENTS.md instructions for SallaApp/ZATCA: See CLAUDE.md for the full guide. Quick facts.
ayunis-legal-mcp CLAUDE.md
Instructions for ayunis-core/ayunis-legal-mcp, covering legal mcp - architecture and development guide, project overview, architecture, directory structure and key components.
korean-firefighter-law-mcp CLAUDE.md
Claude Code instructions for ssd7830-cmyk/korean-firefighter-law-mcp, covering korean-firefighter-law-mcp, a. 답변 규칙 — 기억이 아니라 이 저장소의 코드가 근거다, b. mcp 도구 사용 and c. 작업 규칙.
uae-regulations-registry AGENTS.md
AGENTS.md instructions for nshield-security/uae-regulations-registry, covering agents.md — instructions for ai agents, what this repo contains, preferred entry points, json schema (data/regulations.json) and stable urls.
spain-ai-kit CLAUDE.md
Instructions for aplaceforallmystuff/spain-ai-kit, a project described as: MCP servers connecting AI applications to Spanish government open data and legal infrastructure.
law-mcp CLAUDE.md
Claude Code instructions for finalchild/law-mcp, covering claude.md, build and development commands, architecture overview, core components and key integration points.