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/aplaceforallmystuff/mcp-kit/claude-mdgit clone --depth 1 https://github.com/aplaceforallmystuff/mcp-kitWrote 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/aplaceforallmystuff/mcp-kit/claude-md)<a href="https://agentmods.dev/instructions/aplaceforallmystuff/mcp-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/aplaceforallmystuff/mcp-kit/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 | $0.00644 | $0.00644 |
| Opus 5 | $0.00322 | $0.00322 |
| Sonnet 5 | $0.00129 | $0.00129 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
mcp-kit 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 4d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code when working with this repository.
Project Overview
MCP Kit is a Model Context Protocol server that provides tools for interacting with the Kit.com (formerly ConvertKit) email marketing API. It enables AI assistants to manage subscribers, tags, sequences, broadcasts, forms, custom fields, and webhooks.
Build and Development Commands
# Install dependencies
npm install
# Build TypeScript to JavaScript
npm run build
# Watch mode for development
npm run dev
# Run the server
npm start
Architecture
src/
├── index.ts # MCP server setup, tool definitions, request handlers
└── kit-client.ts # Kit.com API v4 client with typed methods
Data Flow
- MCP client sends tool request →
index.tsvalidates parameters with Zod →KitClientmakes authenticated HTTP request to Kit.com API v4 →- Response formatted and returned to MCP client
Key Patterns
Tool Registration:
server.tool(
"tool_name",
"Tool description",
{ /* Zod schema for parameters */ },
async (params) => {
// Implementation
}
);
API Client Methods:
- All methods in
kit-client.tshandle authentication viaX-Kit-Api-Keyheader - Pagination uses cursor-based approach (
after,per_page) - Returns typed
PaginatedResponse<T>for list operations
Adding New Tools
- Add the API method to
kit-client.ts - Register the tool in
index.tswith appropriate Zod schema - Follow existing patterns for error handling and response formatting
- Rebuild with
npm run build
Environment Variables
| Variable | Required | Description |
|---|---|---|
KIT_API_KEY |
Yes | Kit.com API v4 key |
API Reference
This server uses Kit.com API v4. Documentation: https://developers.kit.com/
Tool Categories
| Category | Tool Count | Description |
|---|---|---|
| Account | 1 | Account information |
| Subscribers | 7 | CRUD + tag management |
| Tags | 6 | CRUD + subscriber listing |
| Sequences | 3 | List, get, add subscribers |
| Broadcasts | 5 | Full CRUD |
| Forms | 3 | List, get, add subscribers |
| Custom Fields | 1 | List fields |
| Webhooks | 3 | CRUD |
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.
- 4d ago First seen · 106 lines · 644 tokens per session scan A 63cdc4030abc
mcp-kit CLAUDE.md is an instructions file published in the GitHub repository aplaceforallmystuff/mcp-kit (4 stars, last pushed 3mo ago), licensed MIT. It adds 644 tokens to every session, about $0.0032 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
mcp AGENTS.md
AGENTS.md instructions for Sequenzy/mcp, covering sequenzy mcp - ai agent instructions, source of truth, sync rules, mcp tool schema compatibility and development.
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
intervals-icu-mcp CLAUDE.md
Instructions for hhopke/intervals-icu-mcp, covering claude.md, project overview, development commands, architecture (quick reference) and tool categories.
ai-toolkit AGENTS.md
AGENTS.md instructions for pipefy/ai-toolkit, covering repository guidelines, documentation map, project structure, import namespace migration: pipefysdk → pipefy and src/pipefysdk/init.py (transitional shim).
flyto-core CLAUDE.md
Claude Code instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.