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/guilhermegouw/context-driven-documentation/claude-mdgit clone --depth 1 https://github.com/guilhermegouw/context-driven-documentationWrote 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/guilhermegouw/context-driven-documentation/claude-md)<a href="https://agentmods.dev/instructions/guilhermegouw/context-driven-documentation/claude-md"><img src="https://agentmods.dev/badge/instructions/guilhermegouw/context-driven-documentation/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.03378 | $0.03378 |
| Opus 5 | $0.01689 | $0.01689 |
| Sonnet 5 | $0.00676 | $0.00676 |
| Haiku 4.5 | $0.00338 | $0.00338 |
Grade A, and why
context-driven-documentation 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 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.
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 — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Constitution
This file serves as the foundational context for all AI-assisted development in this project. Complete this constitution to enable powerful, context-aware AI collaboration.
Project Overview
Project: Context-Driven Documentation (CDD Framework)
Purpose: A complete engineering intelligence system that makes human-AI collaboration feel natural, powerful, and productive.
Target Users: Software engineers and development teams working with AI assistants
Business Domain: Software engineering tools and AI-assisted development
Core Value Proposition: Eliminates the need to repeatedly provide context to AI assistants. Capture your project's context once in structured documentation, and AI assistants immediately understand your project, architecture, and current work - making every conversation start from shared understanding instead of zero.
AI-First Development Philosophy:
- MVP Focus: Claude Code as primary interface - AI-assisted engineering is the core workflow
- Future Vision: Support for additional AI clients while maintaining AI-first approach
- Philosophy: Building for a new paradigm of software development where AI collaboration is fundamental, not supplementary
Architecture & Design Patterns
Architecture Philosophy: AI-First Design - use well-known, conventional patterns that AI assistants can recognize and understand immediately. Favor clarity and familiarity over cleverness.
Core Architectural Patterns:
- Handler Pattern: Separate handlers for different file types (ConstitutionHandler, TicketSpecHandler, etc.) - each knows how to work with its specific file format
- Command Pattern: CLI commands via Click for tooling operations
cdd init- Framework initialization (options: --force, --minimal)cdd new- Ticket and documentation creation with 6 variants:- Tickets: feature, bug, spike, enhancement
- Documentation: guide, feature
- Slash Commands: AI-driven commands (
/socrates,/plan) that turn Claude into specialized personas for intelligent conversations/socrates- Interactive requirements gathering through natural conversation/plan- Autonomous implementation planning with minimal questions
- Template-Driven: Use templates to define structure, AI reads templates to understand what needs to be captured
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.
- 4d ago First seen · 386 lines · 3,378 tokens per session scan A 835aaac09d16
context-driven-documentation CLAUDE.md is an instructions file published in the GitHub repository guilhermegouw/context-driven-documentation (5 stars, last pushed 10mo ago), licensed MIT. It adds 3,378 tokens to every session, about $0.0169 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.
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.