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/aipost-email/mcp-server/claude-mdgit clone --depth 1 https://github.com/AIPOST-EMAIL/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/aipost-email/mcp-server/claude-md)<a href="https://agentmods.dev/instructions/aipost-email/mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/aipost-email/mcp-server/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.00996 | $0.00996 |
| Opus 5 | $0.00498 | $0.00498 |
| Sonnet 5 | $0.00199 | $0.00199 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
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 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — AIPost MCP Server
Version management
- The canonical version is only in
package.json:3("version": "1.1.6"). No other file hardcodes it. smithery.yamlMUST be updated every release. Thenpxarg pins the version explicitly (@aipost/[email protected]). Without a version tag, Smithery's npx cache can serve a stale old version indefinitely — this is why Smithery was stuck on 1.1.1 while npm had 1.1.6.- After pushing
smithery.yamlchanges, rebuild the Smithery deployment on smithery.ai. Smithery readssmithery.yamlat deploy time, not at runtime.
Smithery configSchema
smithery.yamldefines aconfigSchemathat prompts each user for values on the Smithery deployment page.- Adding a new env var that users should configure → add a field to
configSchema.propertiesAND wire it intocommandFunction'senvobject. - Changing
commandFunctiondoes NOT take effect until the deployment is rebuilt on Smithery. - Example:
AIPOST_SENDER_WHITELISTis exposed asaipostSenderWhitelistin the schema.
Windows caveat
- On Windows,
npx -y @aipost/mcp-serverfails because themcp-serverbin entry is not found (shebang issue).- Workaround: use the
aipost-mcpbin instead:npx -y -p @aipost/mcp-server aipost-mcp
- Workaround: use the
- This affects local development on Windows; Smithery runs Linux so it's not affected there.
Sender filter (blacklist / whitelist)
- Controlled by two env vars:
AIPOST_SENDER_WHITELISTandAIPOST_SENDER_BLACKLIST. - Whitelist takes precedence: if both are set, blacklist is ignored.
- The filter applies to all mail/contact tools — inbox, outbox, threads, events, directory, send_message, reply_to, get_message, delete_message. It does NOT apply to
upload_image,upload_audio, orcreate_blog_post(no sender/recipient). - Implementation:
src/filter.ts→SenderFilterclass, used insrc/server.tscreateAipostServer(). - For local stdio MCP clients, set env vars in the MCP client config's
envblock. - For Smithery HTTP deployments, env vars must be configured through the
configSchemaflow (see above).
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 Changed · +25 tokens per session 8bad75df2c88
- 5d ago First seen · 72 lines · 971 tokens per session scan A e7b05ba1749d
mcp-server CLAUDE.md is an instructions file published in the GitHub repository AIPOST-EMAIL/mcp-server (0 stars, last pushed 3d ago), licensed MIT. It adds 996 tokens to every session, about $0.0050 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.
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).
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.
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.
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 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).