Borrowing it
Nothing to install: this file belongs to ckalima/pipedrive-mcp-server. 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/ckalima/pipedrive-mcp-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/ckalima/pipedrive-mcp-serverWrote 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/ckalima/pipedrive-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/ckalima/pipedrive-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/ckalima/pipedrive-mcp-server/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.
<a href="https://agentmods.dev/instructions/ckalima/pipedrive-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/ckalima/pipedrive-mcp-server/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.01497 | $0.01497 |
| Opus 5.5 | $0.00599 | $0.00599 |
| Sonnet 5.5 | $0.00299 | $0.00299 |
| Haiku 4.5 | $0.00150 | $0.00150 |
Grade A, and why
pipedrive-mcp-server 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipedrive MCP Server
MCP server providing Pipedrive CRM tools over STDIO transport. TypeScript, Node.js.
Commands
npm run build # TypeScript compile (tsc)
npm test # Run all tests (vitest)
npm run dev # Dev mode with tsx
npm start # Run compiled server
npm run test:coverage # Coverage report
Architecture
src/
index.ts # MCP server entry point (STDIO transport)
client.ts # Singleton PipedriveClient (lazy init, API calls); drives the resilience retry/breaker loop below fetch
resilience.ts # Retry classifier, full-jitter backoff, Retry-After parsing, per-process circuit breaker (sits below the client chokepoint)
version-routing.ts # v1-only capability seam: routes the four v1 capabilities + lazy sunset/retirement detection (sits above the client)
capability-modes.ts # Resolves PIPEDRIVE_MODE → read-only/safe-write/full; pure tool-reachability classification + tools/list filtering (no new per-tool metadata)
config.ts # Environment validation (PIPEDRIVE_API_KEY, PIPEDRIVE_MODE, PIPEDRIVE_ENABLE_DESTRUCTIVE); shared API-key format predicate + base URLs
identity.ts # Connected-account identity: one bounded GET /users/me (v1) per process at boot, bypassing the version-routing seam; startup banner lines + the one-shot `connection` notice appended to the first tool response
cli/ # `npx … init` guided installer (subcommand routed from index.ts; not the STDIO server path)
init.ts # Interactive flow orchestration + flag parsing; injectable IO seams (readline/opener/validator/writer)
config-targets.ts # Host descriptor table + renderer (per-OS path, top-level key, committed→indirection secret mechanism)
verify-key.ts # Pasted-key validation via createValidationClient → GET /users/me (v1), bypassing the version-routing seam
write-config.ts # Non-destructive config writer (read-merge-backup-atomic write, 0600, symlink/TOCTOU-safe) + `claude mcp add` builder
open-url.ts # Best-effort detached browser opener (env scrubbed of PIPEDRIVE_API_KEY)
tools/ # MCP tool handlers (one file per entity)
index.ts # Tool registration, allTools array, getToolHandler/getToolSchema/getTool
schemas/ # Zod input validation (one file per entity, common.ts for shared)
utils/
errors.ts # Error types, getErrorResponse, destructiveOperationGuard
formatting.ts # createListSummary
pagination.ts # v1 (offset) and v2 (cursor) pagination helpers
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.
- 2mo ago First seen · 87 lines · 1,497 tokens per session scan A 2b42ba11b104
pipedrive-mcp-server CLAUDE.md is an instructions file published in the GitHub repository ckalima/pipedrive-mcp-server (10 stars, last pushed 3d ago), licensed MIT. It adds 1,497 tokens to every session, about $0.0060 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.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.