Borrowing it
Nothing to install: this file belongs to PsychQuant/che-ical-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-ical-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/PsychQuant/che-ical-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-ical-mcp/claude-md)<a href="https://agentmods.dev/instructions/psychquant/che-ical-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/psychquant/che-ical-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.03732 | $0.03732 |
| Opus 5 | $0.01866 | $0.01866 |
| Sonnet 5 | $0.00746 | $0.00746 |
| Haiku 4.5 | $0.00373 | $0.00373 |
Grade A, and why
che-ical-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 6d 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 — 115 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.
MCP 功能驗證的表面選擇（.claude/rules/mcp-binary-version-testing.md）
Binary 更新後 session 內 MCP server 仍是舊版（重啟才換 — 且重啟也不保證換：plugin
wrapper 的 auto-download 會被 Claude Code 的 15 分鐘 connection-failure cache 安靜跳過）。
驗證新功能前必做行為探測（呼叫新版才有的欄位看回應）確認測試表面版本，再依功能性質
選路徑：stateless → --cli 指 repo 內剛 build 的 binary；stateful（undo 等）→ 重啟後的
session MCP tools（--cli per-process stack 結構上驗不了；手動 spawn stdio 有
read-after-write confound）。三表面特性表、wrapper failure-cache 坑與 2026-08-31
#186/v1.16.1 事故記錄見
.claude/rules/mcp-binary-version-testing.md。
Test Naming Convention
Tests/CheICalMCPTests/ follows three filename suffixes that signal what each test exercises. The suffix is load-bearing — pick the right one when adding a new file so reviewers (and Claude) can locate the right test layer fast.
| Filename pattern | Layer | What it tests |
|---|---|---|
<Subject>Tests.swift |
Pure unit | Free functions / value types / pure helpers. No FakeEventKitManager and no EventKitManager instances (static-utility access like EventKitManager.isNonInteractive in SetupCommandTests is fine — it's a type-level probe, not handler integration). Examples: BatchDeleteFilterTests, ReminderCleanupTests, EventKitErrorSanitizerTests, ParticipantFormattingTests, SetupCommandTests. |
<Subject>HandlerTests.swift |
Handler integration | handle* methods from CheICalMCPServer driven through FakeEventKitManager-equivalent doubles. Tests the handler's full sanitize → dispatch → response shape, not the EventKit manager itself. Canonical example: CleanupHandlerTests.swift — copy its structure when adding a new handler test. |
<Subject>DispatchTests.swift |
Outer-catch / dispatch | handleToolCallForTesting outer-catch and the dispatch JSON envelope. Probes what surfaces when a handler throws an unexpected error type. Examples: OuterCatchDispatchTests, DispatchRoundTripTests. |
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.
- 6d ago Changed · +13 lines · +437 tokens per session b7869a7b8a63
- 7d ago First seen · 102 lines · 3,295 tokens per session scan A 4043427f5bd6
che-ical-mcp CLAUDE.md is an instructions file published in the GitHub repository PsychQuant/che-ical-mcp (36 stars, last pushed 2d ago), licensed MIT. It adds 3,732 tokens to every session, about $0.0187 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
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).
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.