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/dixus/claudeframework/claude-mdgit clone --depth 1 https://github.com/dixus/claudeframeworkWhat 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.01363 | $0.01363 |
| Opus 5 | $0.00681 | $0.00681 |
| Sonnet 5 | $0.00273 | $0.00273 |
| Haiku 4.5 | $0.00136 | $0.00136 |
Grade A, and why
claudeframework 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 — 122 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 when working in this repository.
This repo
Claude Code Development Framework — a reusable .claude/ directory with 23 skills, context files, hooks, and documentation that structures Claude Code into a disciplined spec → implement → review → fix → test pipeline with built-in learning.
The src/ directory contains the AI Maturity Score demo app — a working example of the framework applied to a real Next.js/TypeScript project.
To use the framework in a new project: copy the .claude/ directory into your repo and update CLAUDE.md for your tech stack.
Full framework docs: .claude/docs/README.md
Demo app tech stack
| Layer | Technology |
|---|---|
| Framework | Next.js 14 (App Router) + TypeScript |
| Styling | Tailwind CSS + shadcn/ui |
| State | Zustand |
| Charts | Recharts |
| Testing | Vitest + React Testing Library |
| Deploy | Vercel |
Demo app commands
npm run dev # Start dev server
npm run build # Production build (also catches TS errors in JSX)
npm run lint # ESLint
npx tsc --noEmit # Typecheck only
npx vitest run # Run all tests
Demo app architecture
src/
lib/scoring/ # Pure TS scoring engine — no React dependencies
components/ # assessment/ + results/ UI
app/ # Next.js App Router pages
store/ # Zustand state
IMPORTANT: src/lib/scoring/ must remain framework-agnostic pure functions — do not add React dependencies.
Framework skills
Core pipeline
| Skill | Purpose |
|---|---|
/decompose |
Break a concept doc or product brief into independent PRDs, then ship each through the pipeline |
/fleet |
Ship decomposed PRDs in parallel — conflict analysis, batched worktrees, concurrent /ship runs, merge to main |
/ship <feature> |
Full pipeline orchestrator — spec → implement → review → fix → commit. --dry-run runs spec only and reports scope |
/0_spec <feature> |
Write a structured spec from requirements in .claude/input/ |
/1_implement <spec> |
Implement with mandatory plan approval, TDD enforcement, and impact analysis |
/2_review [spec] |
9-lens code review with severity classification and spec completeness check |
/3_fix [review] |
Fix issues by severity (critical → major → minor) with circuit breaker |
/test [file] |
Run typecheck → lint → tests → build (report only, no fixes) |
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 · 122 lines · 1,363 tokens per session scan A 84a6d411e26f
claudeframework CLAUDE.md is an instructions file published in the GitHub repository dixus/claudeframework (10 stars, last pushed 4mo ago), licensed MIT. It adds 1,363 tokens to every session, about $0.0068 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.