code-conductor: Command for Claude Code

.claude/commands/cc-init.md

cc-init is a command for Claude Code from yeisonrestrepo/code-conductor. It costs 11 tokens per session (1,187 once invoked), scanned A, original, MIT.

A project setup command from Conductor that detects the current codebase, identifies its tools and commands, and initializes or updates the project instructions.

In plain words
What is it for?
Use it when starting a new project or bringing an existing one back into sync, so build, test, lint, formatting, and setup commands are recorded.
Why use it?
It reduces manual setup work and fills missing project details while preserving existing non-placeholder instructions in CLAUDE.md.

Command for Claude Code

Written for Claude Code: PreToolUse hook event. Also seen: reads .claude/ paths; mentions CLAUDE.md.

This is yeisonrestrepo/code-conductor's own configuration. It tells Claude Code how to work on code-conductor 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 code-conductor configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node scripts/detect-stack.mjs "$PWD".

Reuse

Borrowing it

Nothing to install: this file belongs to yeisonrestrepo/code-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.

Copy the file
curl -O https://raw.githubusercontent.com/yeisonrestrepo/code-conductor/main/.claude/commands/cc-init.md
Clone the repo
git clone --depth 1 https://github.com/yeisonrestrepo/code-conductor

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 cc-init

README.md
[![agentmods](https://agentmods.dev/badge/commands/yeisonrestrepo/code-conductor/cc-init/github.svg)](https://agentmods.dev/commands/yeisonrestrepo/code-conductor/cc-init)
Your own site
<a href="https://agentmods.dev/commands/yeisonrestrepo/code-conductor/cc-init"><img src="https://agentmods.dev/badge/commands/yeisonrestrepo/code-conductor/cc-init/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 cc-init

Your own site · 80×15
<a href="https://agentmods.dev/commands/yeisonrestrepo/code-conductor/cc-init"><img src="https://agentmods.dev/badge/commands/yeisonrestrepo/code-conductor/cc-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,187 The whole file, excluding the scripts and references it only reads on demand.
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.00011 $0.01187
Opus 5.5 $0.00004 $0.00475
Sonnet 5.5 $0.00002 $0.00237
Haiku 4.5 $0.00001 $0.00119

Measured 8d ago against content hash bc5cc43842e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cc-init 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.

.claude/commands/cc-init.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Step 1 — Detect project state

List files in the project (exclude .git/, .claude/, node_modules/, and dot-files, max depth 3). Count source files found.

If the count is 0 or only CLAUDE.md / config files exist, treat this as a new/empty project (IS_NEW=true). Otherwise set IS_NEW=false.

Step 2 — Auto-detect and collect project identity

If the stack detector is present in the project, run it:

node scripts/detect-stack.mjs "$PWD"

Environment flags: CC_GLOB_DEPTH and any other CC_* env vars the user may have set are automatically inherited by the child node process — no explicit export or forwarding is required. The /cc-init command must NOT reset or unset these variables before calling detect-stack.

Capture the JSON output. For each field in the JSON (name, description, stack, build, test, lint, format, setup), check the corresponding line in CLAUDE.md:

  • If the CLAUDE.md line contains <command> or is blank after Key: → replace with the detected value using a single Edit call.
  • If the CLAUDE.md line already has a non-placeholder value → skip (never overwrite).

Apply all replacements in a single Edit call after collecting all detected values.

If the detector is absent or returns {}, skip auto-detection and continue below.

Step 2b — Resolve what detection could not

Ask about the fields detection could not fill, and never about the ones it did. The script decides which is which; this prose only asks.

node scripts/init-wizard.mjs report

stdout is JSON and nothing else:

{
  "unresolved": [{ "field": "build", "raw": "- Build: <command>", "reason": "placeholder" }],
  "resolved": ["name", "description", "stack", "test"],
  "absent": [{ "field": "setup", "expected": "- Setup:" }]
}

reason is only ever empty or placeholder. stderr carries an advisory summary — never parse it. A non-zero exit means CLAUDE.md is missing or unreadable: stop and report it, do not continue.

Read the full file on GitHub · 112 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. 8d ago Changed bc5cc43842e7
  2. 1mo ago Changed · -5 lines f581fce2298c
  3. 1mo ago Changed · -1 lines 42baa1992355
  4. 1mo ago Changed · +33 lines 6a1e3986fd24
  5. 2mo ago First seen · 85 lines · 11 tokens per session scan A 481b332fa664

Subscribe to this mod's changes

cc-init is a command published in the GitHub repository yeisonrestrepo/code-conductor (17 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 1,187 once invoked, about $0.0000 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.