Borrowing it
Nothing to install: this file belongs to karudo/mcp-component-finder. 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/karudo/mcp-component-finder/main/CLAUDE.mdgit clone --depth 1 https://github.com/karudo/mcp-component-finderWrote 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/karudo/mcp-component-finder/claude-md)<a href="https://agentmods.dev/instructions/karudo/mcp-component-finder/claude-md"><img src="https://agentmods.dev/badge/instructions/karudo/mcp-component-finder/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.00436 | $0.00436 |
| Opus 5 | $0.00218 | $0.00218 |
| Sonnet 5 | $0.00087 | $0.00087 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
mcp-component-finder 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.
What it actually says
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Commands
Build
npm run build
Compiles TypeScript source files from src/ to JavaScript in dist/ using the custom build script at scripts/build.js.
Development
npm run dev
Runs TypeScript compiler in watch mode for development.
Testing
npm test
Runs the test suite located at dist/test.js.
Publishing
npm run publish:npm
Publishes the package to npm using the custom publish script at scripts/publish.js.
Architecture
This is an MCP (Model Context Protocol) server for finding component usage in React/TypeScript projects. The codebase follows a simple architecture:
Core Components
-
ComponentFinder (
src/finder.ts): Main search engine that recursively scans project files to find imports and usages of specified components, functions, or types. Uses regex patterns to detect:- Import statements (named, default, namespace)
- JSX usage
- Function calls
- Type annotations
- Destructuring patterns
-
ComponentFinderMCPServer (
src/server.ts): MCP server implementation that:- Handles JSON-RPC communication via stdin/stdout
- Exposes the
find_component_usagetool - Supports both detailed and files-only output formats
- Uses Russian language for output messages
-
Type Definitions (
src/types.ts): Shared TypeScript interfaces for search options, results, and MCP protocol communication.
MCP Protocol Implementation
The server implements the MCP protocol with:
initialize: Returns server capabilitiestools/list: Lists available tools (currently onlyfind_component_usage)tools/call: Executes the component finder with provided arguments
Configuration
The project can be configured locally via .claude_config.json or globally in Claude Desktop's configuration. The PROJECT_ROOT environment variable determines the search scope.
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 · 61 lines · 436 tokens per session scan A b72dbba84b12
mcp-component-finder CLAUDE.md is an instructions file published in the GitHub repository karudo/mcp-component-finder (0 stars, last pushed 1y ago), licensed MIT. It adds 436 tokens to every session, about $0.0022 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-09-01.
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.