Borrowing it
Nothing to install: this file belongs to szaffarano/org-mcp-server. 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/szaffarano/org-mcp-server/master/CLAUDE.mdgit clone --depth 1 https://github.com/szaffarano/org-mcp-serverWrote 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/szaffarano/org-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/szaffarano/org-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/szaffarano/org-mcp-server/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.01469 | $0.01469 |
| Opus 5 | $0.00734 | $0.00734 |
| Sonnet 5 | $0.00294 | $0.00294 |
| Haiku 4.5 | $0.00147 | $0.00147 |
Grade A, and why
org-mcp-server 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 — 104 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
GitHub repo: https://github.com/szaffarano/org-mcp-server/
MCP server for org-mode knowledge management in Rust. Provides search, content access, agenda views, and note linking for org-mode files through the Model Context Protocol.
Development Commands
cargo build # Build all crates (~47s, never cancel)
cargo test # Run all tests
cargo test <test_name> # Run specific test
cargo test -p <crate_name> # Test specific crate (org-core, org-mcp-server, org-cli)
cargo test --test integration_tests # Run MCP server integration tests
cargo clippy --all-targets --all-features -- -D warnings # Lint
cargo fmt --all # Format code
cargo run --bin org-cli -- --help # Run CLI tool
cargo run --bin org-mcp-server # Run MCP server (needs valid org directory)
cargo run --example <name> # Run playground examples (in org-core/examples/)
Just Commands (available in nix devShell)
just dev # Full workflow: format, lint, test, coverage
just check # Quality gate: fmt-check, lint, test, coverage
just test # Run all tests
just lint # Clippy with -D warnings
just fmt # Format code
just coverage-html # HTML coverage in coverage/html/
Architecture
Rust 2024 edition, multi-crate workspace with async-first design (tokio).
Crate Dependency Flow
org-core <-- org-mcp-server
org-core <-- org-cli
test-utils <-- org-core (dev), org-mcp-server (dev), org-cli (dev)
org-core— All business logic: org-mode parsing (orgize), file discovery (ignorecrate'sWalk), fuzzy search (nucleo-matcher), agenda/task querying, configuration loading (configcrate with TOML/YAML/JSON + env vars). Central type isOrgModestruct (org-core/src/org_mode/types.rs) which holds anOrgConfigand provides all operations. Custom error typeOrgModeErrorinorg-core/src/error.rs.
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 · 104 lines · 1,469 tokens per session scan A c32c0dfed61a
org-mcp-server CLAUDE.md is an instructions file published in the GitHub repository szaffarano/org-mcp-server (42 stars, last pushed 2d ago), licensed MIT. It adds 1,469 tokens to every session, about $0.0073 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.