Borrowing it
Nothing to install: this file belongs to laschopin/better-email-mcp-worker. 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/laschopin/better-email-mcp-worker/main/CLAUDE.mdgit clone --depth 1 https://github.com/laschopin/better-email-mcp-workerWrote 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/laschopin/better-email-mcp-worker/claude-md)<a href="https://agentmods.dev/instructions/laschopin/better-email-mcp-worker/claude-md"><img src="https://agentmods.dev/badge/instructions/laschopin/better-email-mcp-worker/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/laschopin/better-email-mcp-worker/claude-md"><img src="https://agentmods.dev/badge/instructions/laschopin/better-email-mcp-worker/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.02132 | $0.02132 |
| Opus 5 | $0.01066 | $0.01066 |
| Sonnet 5 | $0.00426 | $0.00426 |
| Haiku 4.5 | $0.00213 | $0.00213 |
Grade A, and why
better-email-mcp-worker 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 9d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - better-email-mcp
MCP Server cho Email (IMAP/SMTP). TypeScript, Node.js >= 24, bun, ESM. 5 composite tools, 21 actions (messages, folders, attachments, send, config) plus config__open_relay + help. Multi-account, App Passwords, auto-discovery.
Commands
# Setup
bun install
# Lint & Type check
bun run check # biome check + tsc --noEmit
bun run type-check # tsc --noEmit only
# Fix
bun run check:fix # biome fix + type check
# Test
bun run test # vitest (--passWithNoTests)
bun run test:watch # vitest watch
bun run test:coverage # vitest --coverage
bun vitest run src/tools/helpers/errors.test.ts # single file
# Build & Dev
bun run build # tsc --build tsconfig.build.json + esbuild CLI
bun run dev # tsx watch dev server
# Docker
bun run docker:build
bun run docker:run
# Mise shortcuts
mise run setup # full dev setup
mise run lint # bun run check
mise run test # bun run test
mise run fix # bun run check:fix
Cau truc thu muc
src/
init-server.ts # Entry point, env validation
relay-setup.ts # formatCredentials() helper (relay form fields -> EMAIL_CREDENTIALS string)
relay-schema.ts # Relay form schema (email credential fields)
credential-state.ts # Single-user / stdio credential resolution from env
auth/ # Per-user credential store + Outlook OAuth (HTTP mode)
in-memory-cred-store.ts # LIVE per-user store: ephemeral in-memory, keyed by JWT sub
outlook-device-code.ts # Microsoft device-code OAuth flow
subject-context.ts # Per-request JWT-sub scope (AsyncLocalStorage)
transports/
http.ts # Multi-user HTTP transport with OAuth 2.1
docs/ # Markdown docs phuc vu qua MCP resources
tools/
registry.ts # Tool registration + routing
composite/ # 1 file per domain: messages, folders, attachments, send, config
helpers/ # errors, config, html-utils, imap-client, smtp-client
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.
- 9d ago First seen · 134 lines · 2,132 tokens per session scan A 89781080a5ce
better-email-mcp-worker CLAUDE.md is an instructions file published in the GitHub repository laschopin/better-email-mcp-worker (0 stars, last pushed 1mo ago), licensed MIT. It adds 2,132 tokens to every session, about $0.0107 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
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.
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).
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.