ccpm CLAUDE.md

ccpm CLAUDE.md is an instructions file for coding agents from kaldown/ccpm. It costs 3,031 tokens per session, scanned B, original, MIT.

Repository instructions for organising and reading project documentation, including Claude Code guidance files. A repository is the project folder and its tracked files.

In plain words
What is it for?
Use it when working with architecture notes, feature plans, README files, local instructions, or documentation updates in a kaldown/ccpm project.
Why use it?
It helps an agent find the right project context without confusing shared documentation with personal, machine-specific notes.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/kaldown/ccpm/claude-md
Clone the repo
git clone --depth 1 https://github.com/kaldown/ccpm

Wrote 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.

agentmods badge for ccpm CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/kaldown/ccpm/claude-md.svg)](https://agentmods.dev/instructions/kaldown/ccpm/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/kaldown/ccpm/claude-md"><img src="https://agentmods.dev/badge/instructions/kaldown/ccpm/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 3,031 This file is loaded in full into every session.
When invoked 3,031 The same file — it is already loaded in full.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.03031 $0.03031
Opus 5 $0.01515 $0.01515
Sonnet 5 $0.00606 $0.00606
Haiku 4.5 $0.00303 $0.00303

Measured 4d ago against content hash 2798902a8e3c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

ccpm CLAUDE.md scanned grade B with 1 finding 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 4d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

| `Enter` / `l` / `Space` | Toggle plugin in **Local** scope (`./.claude/settings.local.json`) |
CLAUDE.md · 259 lines

How it starts

The opening of the file, as written. The whole thing — 259 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.

Documentation Hierarchy

This project maintains structured documentation. Read the appropriate files based on context needed.

Committed Documentation (part of repo)

File Purpose When to Read When to Update
CLAUDE.md Primary Claude context, high-to-mid level Auto-read by Claude Code After significant changes
docs/architecture.md Detailed architecture, data models, component hierarchy When making architectural changes or need deep context After structural/architectural changes
FEATURE_PLAN.md Feature tracking, planned/in-progress/completed When planning work or checking status After completing features
README.md User-facing documentation When updating user-facing features Only for significant user-visible changes

Local Documentation (gitignored)

File Purpose When to Read
CLAUDE.local.md Low-level details, links, templates, preferences When need ralph-loop setup, external links, implementation details
.claude/ralph-wiggum-docs.md Ralph-wiggum plugin reference When running ralph-loops
.claude/ccpm-task-*.md Temporal task files During active task execution

Reading Order for Full Context

  1. CLAUDE.md (this file) - Always read first (auto-read)
  2. docs/architecture.md - For architectural understanding
  3. FEATURE_PLAN.md - For current work status
  4. CLAUDE.local.md - For low-level details and templates

Documentation Update Rules

After every significant change:

  1. Architectural changes (new modules, data structures, component changes):

    • Update docs/architecture.md with new/modified structures
    • Update CLAUDE.md if it affects high-level understanding
  2. Feature completion:

    • Update FEATURE_PLAN.md - move to completed section
    • Update CLAUDE.md - remove from in-progress, add to completed if relevant
    • Update CLAUDE.local.md - add implementation details
    • Update docs/architecture.md - if new components/patterns added
    • Bump Cargo.toml version - patch-level (0.x.y0.x.(y+1)) for typical additive features; minor for visible behavior changes that warrant a release marker; major for breaking changes. The bump goes in the same commit as the docs sweep so the version always tracks completed features.

Read the full file on GitHub · 259 lines

Changes

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.

  1. 4d ago First seen · 259 lines · 3,031 tokens per session scan B 2798902a8e3c

Subscribe to this mod's changes

ccpm CLAUDE.md is an instructions file published in the GitHub repository kaldown/ccpm (51 stars, last pushed 4mo ago), licensed MIT. It adds 3,031 tokens to every session, about $0.0152 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens