Borrowing it
Nothing to install: this file belongs to PsychQuant/che-apple-mail-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/PsychQuant/che-apple-mail-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/PsychQuant/che-apple-mail-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/psychquant/che-apple-mail-mcp/claude-md)<a href="https://agentmods.dev/instructions/psychquant/che-apple-mail-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/psychquant/che-apple-mail-mcp/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/psychquant/che-apple-mail-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/psychquant/che-apple-mail-mcp/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.01697 | $0.01697 |
| Opus 5.5 | $0.00679 | $0.00679 |
| Sonnet 5.5 | $0.00339 | $0.00339 |
| Haiku 4.5 | $0.00170 | $0.00170 |
Grade A, and why
che-apple-mail-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 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spectra Instructions
This project uses Spectra for Spec-Driven Development(SDD). Specs live in openspec/specs/, change proposals in openspec/changes/.
Use /spectra:* skills when:
- A discussion needs structure before coding →
/spectra:discuss - User wants to plan, propose, or design a change →
/spectra:propose - Tasks are ready to implement →
/spectra:apply - There's an in-progress change to continue →
/spectra:ingest - User asks about specs or how something works →
/spectra:ask - Implementation is done →
/spectra:archive
Workflow
discuss? → propose → apply ⇄ ingest → archive
discussis optional — skip if requirements are clear- Requirements change mid-work? Plan mode →
ingest→ resumeapply
Parked Changes
Changes can be parked（暫存）— temporarily moved out of openspec/changes/. Parked changes won't appear in spectra list but can be found with spectra list --parked. To restore: spectra unpark <name>. The /spectra:apply and /spectra:ingest skills handle parked changes automatically.
Testing: 測試郵件的收件人只能是維護者自己（CRITICAL，安全規則）
任何會產生、儲存或寄出郵件的測試，To／Cc／Bcc 只能是維護者自己的位址（list_accounts 可查）。適用於 live 測試、手動 smoke、診斷重現、agent 自動測試，人與 agent 都一樣。單元測試（不碰 Mail）不受影響。
禁止：
- 拿真實往來中的信件當
reply_email／forward_email／redirect_email的目標。這三個工具的預設收件人都來自原信，目標選錯，收件人就是真人。 - 在有第三方的信上用
reply_all。 - 用任何真實第三方的位址當測試收件人。
要測 reply／forward／redirect 這類工具，這樣做：
- 先用
compose_email寄一封只寄給自己的測試信（主旨標明「測試」）。 - 在收件匣找到那封信，對它操作。
- 動手前先說出收件人與目標信件，並確認目標信件的寄件人與收件人都只有維護者自己。
- 草稿建出來後，先讀它的
To／Cc，確認只有自己，再做其他事。 - 測完刪除測試草稿與測試信，並回報刪了哪些。
為什麼這是安全邊界，不是風格規則：草稿一旦存在，就只差一次按鍵就寄出，所以 save_as_draft 不算安全邊界。這個 server 自己記錄的失敗模式也說明「只存草稿」不可靠：#461（成功回報但內文為空）、#242（送出階段失敗時寄送狀態未知，信可能已寄出）。2026-10-15 診斷 #510 時，agent 拿真實往來的信件當 reply_email(save_as_draft) 的目標，草稿的預設收件人是真實第三方；沒有寄出，但維護者要求此後一律只寄給自己，並要求寫進本檔（#511）。
Release Process
Releases are published with scripts/release.sh, which bundles the previously
error-prone manual sequence (swift build → git tag → gh release create
→ gh release upload) into one command. Always use the script — the v2.1.1
release was broken because the manual gh release upload step was forgotten
(see #13).
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 Changed · +3 lines · +64 tokens per session cf38d8c35ffc
- 8d ago Changed · +20 lines · +543 tokens per session 0e94b339c30f
- 1mo ago First seen · 97 lines · 1,090 tokens per session scan A 145d7a4cb32f
che-apple-mail-mcp CLAUDE.md is an instructions file published in the GitHub repository PsychQuant/che-apple-mail-mcp (10 stars, last pushed yesterday), licensed MIT. It adds 1,697 tokens to every session, about $0.0068 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).