dox-cc: Instructions file for Claude Code

CLAUDE.md

dox-cc CLAUDE.md is an instructions file for Claude Code from wojciech-zurek/dox-cc. It costs 2,147 tokens per session, scanned A, original, MIT.

A set of instructions for organizing Claude Code guidance in a repository, with one root contract and optional rules that apply only to matching file paths.

In plain words
What is it for?
Use it to structure CLAUDE.md and .claude/rules files, document project conventions, and apply instructions to selected parts of a codebase.
Why use it?
It keeps project rules consistent and prevents unrelated instructions from being loaded everywhere. It also defines where documentation, service, model, and test rules should live.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is wojciech-zurek/dox-cc's own configuration. It tells Claude Code how to work on dox-cc itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dox-cc configures →

Reuse

Borrowing it

Nothing to install: this file belongs to wojciech-zurek/dox-cc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/wojciech-zurek/dox-cc/master/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/wojciech-zurek/dox-cc

Made for: Claude Code.

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 dox-cc CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/wojciech-zurek/dox-cc/claude-md/github.svg)](https://agentmods.dev/instructions/wojciech-zurek/dox-cc/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/wojciech-zurek/dox-cc/claude-md"><img src="https://agentmods.dev/badge/instructions/wojciech-zurek/dox-cc/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for dox-cc CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/wojciech-zurek/dox-cc/claude-md"><img src="https://agentmods.dev/badge/instructions/wojciech-zurek/dox-cc/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,147 This file is loaded in full into every session.
When invoked 2,147 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.02147 $0.02147
Opus 5 $0.01073 $0.01073
Sonnet 5 $0.00429 $0.00429
Haiku 4.5 $0.00215 $0.00215

Measured 12d ago against content hash ecb181ec02d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

dox-cc 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 12d 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.

CLAUDE.md · 190 lines

How it starts

The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DOX framework (Claude Code rules edition)

  • DOX is a highly performant instruction hierarchy for Claude Code
  • The root contract is this file: CLAUDE.md at the repository root (auto-loaded by Claude Code)
  • Domain-specific instructions live in .claude/rules/ as path-scoped rule files
  • Agent must follow DOX instructions across any edits

Doc Layout

  • Root contract: CLAUDE.md (repository root, this file) — global rules, durable workflow, Rules Index
  • Domain rules: .claude/rules/<domain>.md with YAML paths: frontmatter scoping them to project globs
    • services/.claude/rules/services.md with paths: ["services/**"]
    • models/.claude/rules/models.md with paths: ["models/**"]
    • cross-cutting concerns may use extension globs, e.g. .claude/rules/tests.md with paths: ["**/*.test.ts"]
  • Subfolders inside .claude/rules/ are allowed for organization (e.g. .claude/rules/services/auth.md)
  • Rules without a paths: field load unconditionally; use them only for truly global concerns — prefer this root file instead
  • Never create CLAUDE.md files inside project source directories; this root file is the only CLAUDE.md

Rule File Shape

---
paths:
  - "services/auth/**"
---

# Auth Service Rules

## Purpose
## Local Contracts
## Work Guidance
## Creation Conventions
## Verification
  • paths: globs must be quoted when starting with { or *
  • Work Guidance must reflect current project standards; if none exist yet, leave it empty
  • Verification must reflect an existing check; if none exists yet, leave it empty and update it when one exists
  • Creation Conventions lists rules that must hold when NEW files are created in scope (see Known Engine Limits)

Core Contract

  • This root file and every applicable rule file are binding work contracts for their scopes
  • Work products, source materials, instructions, records, assets, and durable docs must stay understandable from the root contract plus every rule whose paths: covers them
  • If docs conflict, the path-scoped rule controls local work details, but no rule may weaken DOX

Read the full file on GitHub · 190 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. 12d ago First seen · 190 lines · 2,147 tokens per session scan A ecb181ec02d7

Subscribe to this mod's changes

dox-cc CLAUDE.md is an instructions file published in the GitHub repository wojciech-zurek/dox-cc (1 stars, last pushed 3mo ago), licensed MIT. It adds 2,147 tokens to every session, about $0.0107 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-31.

Related

Other instructions, from other repositories

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,126 tokens

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.

vercel/next.js · 7,296 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,153 tokens

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

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,469 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