Borrowing it
Nothing to install: this file belongs to danielrosehill/donetick-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/danielrosehill/donetick-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/danielrosehill/donetick-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/danielrosehill/donetick-mcp/claude-md)<a href="https://agentmods.dev/instructions/danielrosehill/donetick-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/danielrosehill/donetick-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.07027 | $0.07027 |
| Opus 5 | $0.03513 | $0.03513 |
| Sonnet 5 | $0.01405 | $0.01405 |
| Haiku 4.5 | $0.00703 | $0.00703 |
Grade A, and why
donetick-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 7d 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.
This is a copy
100% identical to donetick-mcp-server CLAUDE.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 764 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
This is a Model Context Protocol (MCP) server for Donetick chores management. It enables Claude and other MCP-compatible AI assistants to interact with a Donetick instance through a rate-limited API.
Key Technologies:
- Python 3.11+
- MCP SDK (>=1.20.0)
- httpx for async HTTP
- Pydantic for data validation
- Docker for containerization
Project Structure
The project follows a clean directory structure:
donetick-mcp-server/
├── src/donetick_mcp/ # Source code
│ ├── server.py # MCP server implementation
│ ├── client.py # API client with rate limiting
│ ├── models.py # Pydantic data models
│ └── config.py # Configuration management
├── tests/ # Formal test suite (pytest)
│ ├── test_client.py # Unit tests for API client
│ └── test_server.py # Integration tests for MCP server
├── tmp/ # Temporary files (gitignored)
│ └── *.py # Ad-hoc testing, analysis, verification scripts
├── .gitignore # Excludes tmp/, venv/, build artifacts
└── pyproject.toml # Project dependencies and metadata
Important Conventions:
- Source code: Always in
src/donetick_mcp/ - Formal tests: Always in
tests/(run via pytest) - Temporary files: Always in
tmp/for analysis, verification, one-off testing - Never commit: Files in
tmp/are gitignored - use for local experimentation only
When creating test scripts for verification or analysis, always place them in tmp/ to keep the project root clean. The formal test suite in tests/ should be reserved for permanent, repeatable tests that are part of CI/CD.
Development Commands
Setup & Installation
# Create virtual environment
python -m venv venv
source venv/bin/activate # On Windows: venv\Scripts\activate
# Install for development
pip install -e ".[dev]"
# Install production only
pip install -e .
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.
- 7d ago First seen · 764 lines · 7,027 tokens per session scan A 2ceec0d43b52
donetick-mcp CLAUDE.md is an instructions file published in the GitHub repository danielrosehill/donetick-mcp (2 stars, last pushed 5mo ago), licensed MIT. It adds 7,027 tokens to every session, about $0.0351 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to donetick-mcp-server CLAUDE.md, differing in 0 lines, and is treated as a copy.
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.