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/comma-compliance/pipedrive-mcp/claude-mdgit clone --depth 1 https://github.com/comma-compliance/pipedrive-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/comma-compliance/pipedrive-mcp/claude-md)<a href="https://agentmods.dev/instructions/comma-compliance/pipedrive-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/comma-compliance/pipedrive-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.00284 | $0.00284 |
| Opus 5 | $0.00142 | $0.00142 |
| Sonnet 5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
pipedrive-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.
What it actually says
Pipedrive MCP Server
Build instructions
- npm install && npm run build
- npm run dev (watch mode)
- npm test (vitest)
Architecture rules
- One tool file per entity in src/tools/
- One schema file per entity in src/schemas/
- No business logic in tool handlers - delegate to services/
- No raw HTTP in tool files - use api-v1.ts or api-v2.ts via http-client.ts
- No @ts-ignore - fix types properly
- No hardcoded Pipedrive field keys or option IDs
- All destructive tools require confirm param and support dry_run
- Use native fetch (not axios)
- Use Zod .strict() on all tool input schemas
- v2 activities use participants array, not person_id (which is read-only)
- v2 custom field writes must nest fields in a custom_fields object
- All field metadata endpoints are v1 (v2 field routes are not available on all instances)
Testing
- vitest for all tests
- nock for HTTP mocking in integration tests
- Never hit production Pipedrive in tests
- Sanitized fixtures in test/fixtures/v1/ and test/fixtures/v2/
Key files
- src/pipedrive/endpoint-policy.ts is the source of truth for API routing
- src/services/custom-fields.ts handles all field name resolution
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 · 31 lines · 284 tokens per session scan A 9bef64cd584a
pipedrive-mcp CLAUDE.md is an instructions file published in the GitHub repository comma-compliance/pipedrive-mcp (8 stars, last pushed 4mo ago), licensed MIT. It adds 284 tokens to every session, about $0.0014 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
pfsense-mcp-server AGENTS.md
AGENTS.md instructions for night4me/pfsense-mcp-server, covering pfsense mcp server, architecture and security, development workflow, long-running validation and test parallelism.
sui-mcp CLAUDE.md
Claude Code instructions for 0xfreak0/sui-mcp, covering sui-mcp, stack, architecture, which transport to use and archive fallback.
pdf-toolkit-mcp CLAUDE.md
Instructions for AryanBV/pdf-toolkit-mcp, covering pdf-toolkit-mcp, 1. project overview, 2. tech stack, 3. project structure and 4. mcp sdk patterns.
clawstash CLAUDE.md
Claude Code instructions for fo0/clawstash, covering claude.md -- project guide, session start -- read order, workflow triggers, output languages and performance / modes.
datadog-mcp CLAUDE.md
Claude Code instructions for dreamiurg/datadog-mcp, covering agent instructions, project, stack, commands and releases.
pubmed-mcp-server AGENTS.md
AGENTS.md instructions for cyanheads/pubmed-mcp-server, covering agent protocol, what's next?, core rules, patterns and tool.