Borrowing it
Nothing to install: this file belongs to rbarcante/claude-conductor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rbarcante/claude-conductor/master/CLAUDE.mdgit clone --depth 1 https://github.com/rbarcante/claude-conductorWrote 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/rbarcante/claude-conductor/claude-md)<a href="https://agentmods.dev/instructions/rbarcante/claude-conductor/claude-md"><img src="https://agentmods.dev/badge/instructions/rbarcante/claude-conductor/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.1 | $0.00984 | $0.00984 |
| Opus 5 | $0.00492 | $0.00492 |
| Sonnet 5 | $0.00197 | $0.00197 |
| Haiku 4.5 | $0.00098 | $0.00098 |
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 8d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conductor Context
If a user mentions a "plan" or asks about the plan, and they have used the claude conductor in the current session, they are likely referring to one of the track plans (conductor/tracks/<track_id>/plan.md).
Universal File Resolution Protocol
PROTOCOL: How to locate files. To find a file (e.g., "Product Definition") within a specific context (Project Root or a specific Track):
-
Identify Index: Determine the relevant index file:
- Project Context:
conductor/index.md - Track Context:
a. Resolve and read the Tracks Registry (via Project Context).
b. Find the entry for the specific
<track_id>. c. Follow the link provided in the registry to locate the track's folder. The index file is<track_folder>/index.md. d. Fallback: If the track is not yet registered (e.g., during creation) or the link is broken: 1. Resolve the Tracks Directory (via Project Context). 2. The index file is<Tracks Directory>/<track_id>/index.md.
- Project Context:
-
Check Index: Read the index file and look for a link with a matching or semantically similar label.
-
Resolve Path: If a link is found, resolve its path relative to the directory containing the
index.mdfile.- Example: If
conductor/index.mdlinks to./workflow.md, the full path isconductor/workflow.md.
- Example: If
-
Fallback: If the index file is missing or the link is absent, use the Default Path keys below.
-
Verify: You MUST verify the resolved file actually exists on the disk.
Standard Default Paths (Project):
- Product Definition:
conductor/product.md - Tech Stack:
conductor/tech-stack.md - Workflow:
conductor/workflow.md - Product Guidelines:
conductor/product-guidelines.md - Tracks Directory:
conductor/tracks/
Standard Default Paths (Track):
- Specification:
conductor/tracks/<track_id>/spec.md - Implementation Plan:
conductor/tracks/<track_id>/plan.md - Metadata:
conductor/tracks/<track_id>/metadata.json
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.
- 8d ago First seen · 86 lines · 984 tokens per session scan A 73c5032fed3f
claude-conductor CLAUDE.md is an instructions file published in the GitHub repository rbarcante/claude-conductor (56 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 984 tokens to every session, about $0.0049 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.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.