Borrowing it
Nothing to install: this file belongs to wyattjoh/jmap-mcp. 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/wyattjoh/jmap-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/wyattjoh/jmap-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/wyattjoh/jmap-mcp/claude-md)<a href="https://agentmods.dev/instructions/wyattjoh/jmap-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/wyattjoh/jmap-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.01085 | $0.01085 |
| Opus 5 | $0.00543 | $0.00543 |
| Sonnet 5 | $0.00217 | $0.00217 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
jmap-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 8d 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 — 120 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 (claude.ai/code) when working with code in this repository.
Project Overview
This is a Model Context Protocol (MCP) server that provides JMAP (JSON Meta Application Protocol) email management tools. It's built with Deno and integrates with JMAP-compliant email servers like FastMail, Cyrus IMAP, and Stalwart Mail Server.
Development Commands
deno task start- Run the MCP serverdeno task watch- Run with file watchingdeno check- Type-check the projectdeno fmt- Format code (excludes CHANGELOG.md)deno lint- Lint the projectdeno test --allow-env --allow-net- Run all testsdeno test --allow-env --allow-net src/tools/email_test.ts- Run a single test filedeno publish --dry-run --allow-dirty- Validate JSR publish
Pre-commit Hooks
Run deno task hooks:install to set up git hooks. Pre-commit runs
deno check && deno fmt --check && deno lint. Pre-push runs
deno publish --dry-run --allow-dirty.
Required Environment Variables
JMAP_SESSION_URL="https://your-jmap-server.com/.well-known/jmap"
JMAP_BEARER_TOKEN="your-bearer-token"
JMAP_ACCOUNT_ID="account-id" # Optional, auto-detected if not provided
Architecture
Core Structure
- Entry point:
src/mod.ts- MCP server setup, JMAP client initialization, and tool registration - Tool modules:
src/tools/- Modular tool implementationsemail.ts- Email search, retrieval, mailbox management, and basic operationssubmission.ts- Email composition and sending (when JMAP submission capability is available)
- Utilities:
src/utils.ts- Common utilities like error formatting
Key Design Patterns
- Functional programming style - Functions are pure where possible, side effects are contained
- Runtime validation - All inputs validated with Zod schemas before processing
- Capability-based registration - Tools are registered based on JMAP server
capabilities (checked in
mod.tsviasession.capabilities) - Graceful degradation - Server adapts to read-only accounts and limited JMAP capabilities
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.
- 8d ago First seen · 120 lines · 1,085 tokens per session scan A 9009ca3b7463
jmap-mcp CLAUDE.md is an instructions file published in the GitHub repository wyattjoh/jmap-mcp (176 stars, last pushed 4d ago), licensed MIT. It adds 1,085 tokens to every session, about $0.0054 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-30.
Other instructions, from other repositories
vibe-coding-prompt-template backend.instructions.md
Instructions for KhazP/vibe-coding-prompt-template: Read AGENTS.md, agentdocs/techstack.md, and agentdocs/codepatterns.md.
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).
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).