Atomic-Spec: Instructions file for Claude Code

CLAUDE.md

Atomic-Spec CLAUDE.md is an instructions file for Claude Code from Chappygo-OS/Atomic-Spec. It costs 3,372 tokens per session, scanned A, original, MIT.

A governance framework that guides AI coding agents through gated phases such as specifying, planning, breaking work into tasks, and implementing it. It uses templates, prompts, knowledge files, and a small command-line tool.

In plain words
What is it for?
Use it to prepare projects for controlled AI-assisted development and to keep features linked to their specifications, plans, and individual tasks.
Why use it?
It reduces the risk of an AI agent drifting from the agreed requirements while generating code.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

This is Chappygo-OS/Atomic-Spec's own configuration. It tells Claude Code how to work on Atomic-Spec 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 Atomic-Spec configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Chappygo-OS/Atomic-Spec. 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/Chappygo-OS/Atomic-Spec/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/Chappygo-OS/Atomic-Spec

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 Atomic-Spec CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/chappygo-os/atomic-spec/claude-md/github.svg)](https://agentmods.dev/instructions/chappygo-os/atomic-spec/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/chappygo-os/atomic-spec/claude-md"><img src="https://agentmods.dev/badge/instructions/chappygo-os/atomic-spec/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 Atomic-Spec CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/chappygo-os/atomic-spec/claude-md"><img src="https://agentmods.dev/badge/instructions/chappygo-os/atomic-spec/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,372 This file is loaded in full into every session.
When invoked 3,372 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.03372 $0.03372
Opus 5.5 $0.01349 $0.01349
Sonnet 5.5 $0.00674 $0.00674
Haiku 4.5 $0.00337 $0.00337

Measured 1mo ago against content hash 03a20b0c3f69, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Atomic-Spec 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 1mo 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 · 200 lines

How it starts

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

What This Repository Is

This is not a runtime application. It is a governance framework for AI-driven development — a customized fork of GitHub's Spec Kit that implements the Atomic Traceability Model. The deliverables are templates, prompts, knowledge stations, and a thin Python CLI. Consumers install this framework into their own projects to constrain how AI coding agents (Claude Code, Gemini, Copilot, Cursor, Windsurf, and ~13 others) generate code.

Inspired by Leapable's "Stop Vibe Coding (Until You Do This)" video. The core premise: AI agents produce drift unless forced through gated, atomic, context-pinned phases.

The Nine Prime Directives (memory/constitution.md, Article IX)

These are the non-negotiable rules that every command in this framework enforces. When working in this repo, never weaken or bypass them — they are the entire value proposition:

  1. Directory Supremacy — every feature gets index.md + traceability.md
  2. Atomic Injunction — /atomicspec.tasks is FORBIDDEN from creating a single tasks.md. It must create a tasks/ directory with individual T-XXX-[name].md files
  3. Context Pinning — during /atomicspec.implement, the AI may ONLY read index.md, the current task file, and traceability.md. Reading plan.md or spec.md during implementation is forbidden
  4. Gate Compliance — Knowledge Station gate criteria must pass before phase transitions
  5. Knowledge Routing — unknown decisions consult the Station Map first, then the specific station
  6. Human-In-The-Loop — /atomicspec.plan pauses at 4 mandatory checkpoints (tech stack, validation, UI, registry sync). v0.5+ adds an optional derivation checkpoint (Phase 0.85 — Test Strategy Derivation, HITL #3.5) that inherits the D6 contract; the 4-floor stays. Composes alongside, never replaces.
  7. Project Defaults Registry — all commands read specs/_defaults/registry.yaml and enforce project-wide standards
  8. Self-Contained Tasks — task files embed all context (registry values, domain rules, gate criteria) needed for execution under Context Pinning
  9. Orientation Read Surface (v0.3+) — /atomicspec.implement Phase 0 detects cross-provider handoff state via stamp-lifecycle status on artifact Lifecycle Markers; direct body reads of plan.md / spec.md / clarify-log.md remain forbidden, even during orientation. Sibling control to Directive 3; does NOT widen it.

Read the full file on GitHub · 200 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. 1mo ago Changed · +50 tokens per session 03a20b0c3f69
  2. 1mo ago First seen · 200 lines · 3,322 tokens per session scan A 61484038ee2d

Subscribe to this mod's changes

Atomic-Spec CLAUDE.md is an instructions file published in the GitHub repository Chappygo-OS/Atomic-Spec (10 stars, last pushed 1mo ago), licensed MIT. It adds 3,372 tokens to every session, about $0.0135 per session on Opus 5.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

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 · 9,715 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,461 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens