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.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.01090 | $0.01090 |
| Opus 5 | $0.00545 | $0.00545 |
| Sonnet 5 | $0.00218 | $0.00218 |
| Haiku 4.5 | $0.00109 | $0.00109 |
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 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 — 97 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.
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).
Publishing a new release
Prerequisites:
- CHANGELOG.md has a new
## [X.Y.Z]section with the release notes - HEAD is on
main, working tree is clean, and the commit is pushed to origin ghCLI is authenticated
Run:
./scripts/release.sh vX.Y.Z
# or, with a custom title:
./scripts/release.sh vX.Y.Z "vX.Y.Z: short description"
The script will:
- Sanity-check the working tree, tag absence, and CHANGELOG entry
- Extract release notes from CHANGELOG.md's
[X.Y.Z]section - Build a universal (arm64 + x86_64) binary into
.build/dist/ - Confirm with you before any destructive / remote operation
- Sign + notarize the binary (Developer ID), unless
SKIP_CODESIGN=1or noDEVELOPER_IDis set - Create git tag
vX.Y.Z, push to origin - Create GitHub release and upload the signed binary +
.sha256
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 · 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 (8 stars, last pushed yesterday), licensed MIT. It adds 1,090 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
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.
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.