claude-conductor CLAUDE.md

A documentation guide for Claude Conductor, a modular set of Markdown files that helps Claude Code work consistently on a project. It describes the main documentation file and planned areas such as architecture, configuration, APIs, builds, and testing.

In plain words
What is it for?
Use it when Claude Code needs to understand or extend the project's documentation system, architecture, development setup, or contribution guidance.
Why use it?
It gives the coding agent a shared project map and important rules, including preserving and summarising journal history instead of deleting it.

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/superbasicstudio/claude-conductor/claude-md
Clone the repo
git clone --depth 1 https://github.com/superbasicstudio/claude-conductor
Per session 2,156 This file is loaded in full into every session.
When invoked 2,156 The same file — it is already loaded in full.
Security scan A 0 findings. 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.02156 $0.02156
Opus 5 $0.01078 $0.01078
Sonnet 5 $0.00431 $0.00431
Haiku 4.5 $0.00216 $0.00216

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

Security

Grade A, and why

claude-conductor 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 2d 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 · 209 lines

How it starts

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

Critical Context (Read First)

  • Tech Stack: Documentation framework (Markdown)
  • Main File: CONDUCTOR.md (437 lines)
  • Core Mechanic: Modular documentation system for AI-assisted development
  • Key Integration: Claude Code AI assistant
  • Platform Support: Any project using Claude Code
  • DO NOT: Delete raw history from JOURNAL.md - only move & summarize

Project Architecture

This is a documentation framework designed to work with Claude Code AI assistant. The system provides:

Core Component

  • CONDUCTOR.md (CONDUCTOR.md:1-437) - Master template that defines the entire documentation system

Planned Documentation Modules

The framework defines 13 interconnected documentation files:

  1. ARCHITECTURE.md - Tech stack and system design
  2. DESIGN.md - Visual design system
  3. UIUX.md - User interaction patterns
  4. CONFIG.md - Runtime configuration
  5. DATA_MODEL.md - Database schema
  6. API.md - API documentation
  7. BUILD.md - Build and deployment
  8. TEST.md - Testing strategies
  9. CONTRIBUTING.md - Contributor guidelines
  10. PLAYBOOKS/DEPLOY.md - Operational procedures
  11. ERRORS.md - Critical error tracking
  12. JOURNAL.md - Development changelog

Development Workflow

Since this is a documentation framework, the typical workflow is:

  1. Start with CONDUCTOR.md - Review the template structure
  2. Create project-specific CLAUDE.md - Adapt this template for target project
  3. Implement documentation modules - Create the 13 files as needed
  4. Set up journaling system - Begin tracking changes in JOURNAL.md
  5. Maintain cross-links - Keep documentation interconnected
  6. Archive when needed - Move old journal entries when exceeding 500 lines

Key Features

Line Number Anchors (CONDUCTOR.md:278-284)

  • Documents require exact line numbers for code references
  • Format: **Class Name (Lines 100-200)**
  • HTML anchors: <!-- #class-name -->

Read the full file on GitHub · 209 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. 2d ago First seen · 209 lines · 2,156 tokens per session scan A 5dbefc95dba6

Subscribe to this mod's changes

claude-conductor CLAUDE.md is an instructions file published in the GitHub repository superbasicstudio/claude-conductor (380 stars, last pushed 3mo ago), licensed BSD-2-Clause. It adds 2,156 tokens to every session, about $0.0108 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-30.