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/gravitykit/drip-mcp-server/agents-mdgit clone --depth 1 https://github.com/GravityKit/drip-mcp-serverWhat 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 | $0.02447 | $0.02447 |
| Opus 5 | $0.01223 | $0.01223 |
| Sonnet 5 | $0.00489 | $0.00489 |
| Haiku 4.5 | $0.00245 | $0.00245 |
Grade A, and why
drip-mcp-server AGENTS.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 yesterday.
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 — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Drip MCP Server
This file contains guidance for agents and contributors working within the drip-mcp-server package. Its scope is this directory and all subfolders.
Project Overview
The Drip MCP Server is a Model Context Protocol implementation that provides AI assistants with access to the Drip email marketing platform API. It enables subscriber management, campaign automation, workflow control, and analytics tracking through standardized MCP tools.
Core Principles
- Portability First: Avoid absolute paths; prefer relative paths from the package root and dynamic path resolution
- Security by Default: Never commit secrets; read environment from
.envor the host MCP client - Minimal Dependencies: Keep the server lean; rely on Drip's API and standard Node libraries
- Clear Errors: All tool failures should include actionable messages with remediation steps
- User-Friendly: Automatic field mapping, rate limiting, and error recovery
Tech Stack
- Runtime: Node.js 20+ (ESM only)
- HTTP Client:
axios^1.7.9 for Drip API communication - MCP SDK:
@modelcontextprotocol/sdk^1.0.0 for protocol implementation - Environment:
dotenv^16.4.7 for local environment loading (optional) - Testing: Native Node.js test runner with custom test framework
Architecture
drip-mcp-server/
├── src/
│ ├── index.js # MCP server implementation & tool handlers
│ ├── drip-client.js # Drip API client with rate limiting
│ └── tests/ # Comprehensive test suites
│ ├── run.js # Test runner with fallback support
│ ├── drip-client.test.js # Unit tests for API client
│ ├── server-tools.test.js # Tool validation tests
│ └── server-e2e.test.js # End-to-end integration tests
├── package.json # Dependencies and scripts
├── mcp.json # MCP Inspector configuration
├── .env.example # Environment template
├── CLAUDE.md # This file - agent guidance
├── LICENSE # MIT license
└── README.md # Public documentation
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.
- yesterday First seen · 315 lines · 2,447 tokens per session scan A b6db86f82d69
drip-mcp-server AGENTS.md is an instructions file published in the GitHub repository GravityKit/drip-mcp-server (0 stars, last pushed 11mo ago), licensed MIT. It adds 2,447 tokens to every session, about $0.0122 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
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.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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.
langchain 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.