Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/mattydsmith/things-cloud-mcp/claude-mdgit clone --depth 1 https://github.com/mattydsmith/things-cloud-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/mattydsmith/things-cloud-mcp/claude-md)<a href="https://agentmods.dev/instructions/mattydsmith/things-cloud-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/mattydsmith/things-cloud-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 | $0.01410 | $0.01410 |
| Opus 5 | $0.00705 | $0.00705 |
| Sonnet 5 | $0.00282 | $0.00282 |
| Haiku 4.5 | $0.00141 | $0.00141 |
Grade A, and why
things-cloud-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 3d 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
Go SDK for the Things 3 cloud API (Cultured Code). This is a reverse-engineered, unofficial SDK — there is no official API documentation. The client mimics ThingsMac/32209501 and sends a base64-encoded things-client-info device metadata header.
Build & Test Commands
go build -v ./... # Build all packages
go test -v ./... # Run all tests
go test -v -run TestName # Run a single test
go test -v ./state/memory # Run tests for a specific package
go test -v ./sync # Run sync engine tests
go generate # Regenerate stringer methods (itemaction_string.go)
Architecture
All source code lives at the package root (package things), with two sub-packages:
state/memory— In-memory state aggregation (for testing/simple use)sync— Persistent SQLite-backed sync engine with semantic change detection
Core Design: Event-Sourced Sync
The SDK models all changes as immutable Items (events). A History is a sync stream identified by a UUID. The client pushes/pulls Items through Histories to stay in sync with the Things Cloud server.
client.go— HTTP client withClientInfoheader and configurableDebuglogging, base endpointhttps://cloud.culturedcode.comhistories.go— History CRUD and sync operations (list, create, delete, read/write items with ancestor indices). TheWrite()method accepts multiple items for batching.items.go— Item construction: every mutation (create/modify/delete) on a Task, Area, Tag, CheckListItem, or Tombstone produces an Itemtypes.go— Domain types:Task(withTaskTypeenum: Task/Project/Heading),Area,Tag,CheckListItem,Tombstone, plus custom JSON types (Timestamp,Boolean)notes.go— StructuredNotetype with full-text and delta patch support (ApplyPatches)repeat.go— Recurring task date calculation (daily/weekly/monthly/yearly, with end conditions)helpers.go— Pointer helpers (String(),Status(),Schedule(),Time(),TaskTypePtr())account.go— AccountService for signup, confirmation, password change, deletionapp_instance.go— Device registration for APNS push notifications
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.
- 3d ago First seen · 104 lines · 1,410 tokens per session scan A 3d427d6b8403
things-cloud-mcp CLAUDE.md is an instructions file published in the GitHub repository mattydsmith/things-cloud-mcp (20 stars, last pushed 5mo ago), licensed MIT. It adds 1,410 tokens to every session, about $0.0070 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
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.