icfmcp: Instructions file for Claude Code

CLAUDE.md

icfmcp CLAUDE.md is an instructions file for Claude Code from icformat/icfmcp. It costs 1,523 tokens per session, scanned A, original, MIT.

A repository guide for Claude Code, covering how the icfmcp TypeScript project is built, tested, structured, and connected to the related icf.js library. It also points to the specifications that govern its index behaviour.

In plain words
What is it for?
Use it when modifying icfmcp, running its build, tests, or type checks, or changing how it exposes ICF knowledge files through the Model Context Protocol (MCP), a standard way for AI tools to access external data and functions.
Why use it?
It gives the coding agent the project rules and reference documents it needs before changing code, reducing the risk of breaking builds or index formats.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is icformat/icfmcp's own configuration. It tells Claude Code how to work on icfmcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything icfmcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to icformat/icfmcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/icformat/icfmcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/icformat/icfmcp

Made for: Claude Code.

Wrote 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.

agentmods badge for icfmcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/icformat/icfmcp/claude-md/github.svg)](https://agentmods.dev/instructions/icformat/icfmcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/icformat/icfmcp/claude-md"><img src="https://agentmods.dev/badge/instructions/icformat/icfmcp/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.

agentmods 80×15 button for icfmcp CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/icformat/icfmcp/claude-md"><img src="https://agentmods.dev/badge/instructions/icformat/icfmcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,523 This file is loaded in full into every session.
When invoked 1,523 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01523 $0.01523
Opus 5.5 $0.00609 $0.00609
Sonnet 5.5 $0.00305 $0.00305
Haiku 4.5 $0.00152 $0.00152

Measured 2mo ago against content hash ff9e095ed6ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

icfmcp 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 2mo 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.

CLAUDE.md · 55 lines

How it starts

The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

Guidance for Claude Code when working in this repository.

What this repo is

icfmcp is an MCP (Model Context Protocol) server, written in TypeScript (ESM, Node >= 20), that exposes ICF knowledge files to AI harnesses through their ICX indexes. It consumes the sibling icf.js library as a file dependency ("icf.js": "file:../icf.js" — the npm registry copy is older than the local build).

Specs (read before changing index semantics):

  • ICF language spec v1.1: F:\git\GreenbooksGithub\icformat.org\icf\specification\v1.1\
  • ICX index spec v1.2: F:\git\GreenbooksGithub\icformat.org\icx\specification\v1.2\ — §7 Tags, §8 Summary, §9 inverted structures (tagindex[]/summaryindex[]), §15 harness usage flow.
  • icf.js API reference: F:\git\GreenbooksGithub\icf.js\DOCUMENTATION.md

Build & test

npm run build      # tsc -> dist/ (dist/index.js keeps the #!/usr/bin/env node shebang; bin "icfmcp")
npm test           # vitest against tests/fixtures — no MCP transport needed
npm run typecheck  # tsc --noEmit for src (tsconfig.json) and tests (tsconfig.test.json)
npm run dev -- tests/fixtures

Architecture

src/index.ts is only MCP wiring (CLI args → DocumentRegistry, zod tool schemas → McpServer, stdio transport). All logic lives in pure, transport-free modules — tests exercise them directly:

  • src/registry.ts — DocumentRegistry. Discovers .icf files (directories scanned recursively, skipping dotdirs/node_modules), keys each by its file stem (duplicates suffixed -2, -3, … in sorted-path order), and caches parsed entries by mtime+size of both the ICF and its ICX. refresh() is called by every tool and is cheap when nothing changed; it also reloads when a sibling .icx appears/disappears and drops vanished files. Index acquisition per document: the ICF's @index directive target first, then the same-stem sibling .icx; if neither exists, generateIcx(doc) in memory.
  • src/indexing.ts — extractIndexModel(icxDoc, masterTypes) turns a parsed/generated ICX document into an IndexModel (rows + tagIndex + summaryIndex). Two quirks it absorbs: a hand-written ICX exposes master rows via getMasters() and data rows/tagindex[]/summaryindex[] inside one implicit record; a generateIcx document puts all collections (master types included) in one synthetic record — hence the masterTypes hint from the source document. augmentFromSource(...) then fills gaps from the source ICF: missing Line/Offset/Size from scanned spans, missing tags by harvesting typed master references (ICX §7 generator rule), missing summaries from a summary attribute/field, and synthesizes rows for records the index doesn't know.
  • src/source.ts — scanRecordBlocks finds column-0 @record lines, returning per-record byte offset/size, 1-based start line, id=, and the raw block text. Raw blocks are always taken from this scan (never by ICX byte ranges) so stale indexes can't corrupt output. Known limitation: a column-0 @record inside a preformatted text block would miscount; spans are correlated with parsed records by id first, by order only when counts agree.
  • src/tags.ts — ICX §7 tag-cell handling. Feature-detects icf.js 1.2 splitTags/joinTags exports and falls back to a local implementation (join +, escape \, \+ = literal plus). Keep the fallbacks and their direct tests even after icf.js 1.2 is everywhere.
  • src/tools.ts — the seven tool functions, all (registry, args) -> JSON-serializable object. Recoverable problems return { error, ... } (checked with isToolError), never throw; src/index.ts maps that to isError: true and always emits a single JSON text content block.

Read the full file on GitHub · 55 lines

Changes

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.

  1. 2mo ago First seen · 55 lines · 1,523 tokens per session scan A ff9e095ed6ac

Subscribe to this mod's changes

icfmcp CLAUDE.md is an instructions file published in the GitHub repository icformat/icfmcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 1,523 tokens to every session, about $0.0061 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.

Related

icfmcp CLAUDE.md compared with instructions from other repositories

icfmcp CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
icfmcp CLAUDE.mdicformat/icfmcpInstructions file03mo agoMITA1,523Claude Code
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file196ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file144ktodayMITA8,130Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file196ktodayMITA5,685GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file150ktodayMITA4,680Codex, OpenCode
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file283ktodayMITA4,342Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file196ktodayMITA3,153GitHub Copilot