help

A help guide for Conductor, a development workflow for Claude Code that keeps project context, specifications, plans, and progress alongside the code. It uses approval points and linked Git commits to track implementation.

In plain words
What is it for?
Use it to set up Conductor, create development tracks, write requirements and implementation plans, run planned tasks, and check project status.
Why use it?
It helps teams understand the workflow before coding and maintain a clear record of what is being built, how it should be built, and what has been completed.

Skill for Claude CodeCodex

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 skills/madappgang/claude-code/help
Any agent
npx skills add MadAppGang/claude-code --skill help
Clone the repo
git clone --depth 1 https://github.com/MadAppGang/claude-code

Made for: Claude Code, Codex.

Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 726 The whole file, excluding the scripts and references it only reads on demand.
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.00016 $0.00726
Opus 5 $0.00008 $0.00363
Sonnet 5 $0.00003 $0.00145
Haiku 4.5 $0.00002 $0.00073

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

Security

Grade A, and why

help 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.

plugins/conductor/skills/help/SKILL.md · 104 lines

How it starts

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

plugin: conductor updated: 2026-01-20

Conductor Help

Conductor implements Context-Driven Development for Claude Code.

Philosophy

Context as a Managed Artifact: Your project context (goals, tech stack, workflow) is documented and maintained alongside your code. This context guides all development work.

Pre-Implementation Planning: Before coding, create a spec (WHAT) and plan (HOW). This ensures clear direction and traceable progress.

Safe Iteration: Human approval gates at key points. Git-linked commits for traceability. Easy rollback when needed.

Available Skills

conductor:setup

Initialize Conductor for your project.

  • Creates conductor/ directory structure
  • Generates product.md, tech-stack.md, workflow.md
  • Interactive Q&A with resume capability

conductor:new-track

Create a new development track.

  • Generates spec.md with requirements
  • Creates hierarchical plan.md (phases -> tasks)
  • Updates tracks.md index

conductor:implement

Execute tasks from your plan.

  • Status progression: [ ] -> [~] -> [x]
  • Git commits linked to track/task
  • Follows workflow.md procedures

conductor:status

View project progress.

  • Overall completion percentage
  • Current task and blockers
  • Multi-track overview

conductor:revert

Git-aware logical undo.

  • Revert at Track, Phase, or Task level
  • Preview before executing
  • State validation after revert

Quick Start

  1. Initialize: Run conductor:setup to create context files
  2. Plan: Run conductor:new-track to create your first track
  3. Implement: Run conductor:implement to start working
  4. Check: Run conductor:status to see progress
  5. Undo: Run conductor:revert if you need to roll back

Directory Structure

conductor/
├── product.md          # Project vision and goals
├── tech-stack.md       # Technical preferences
├── workflow.md         # Development procedures
├── tracks.md           # Index of all tracks
└── tracks/
    └── {track_id}/
        ├── spec.md     # Requirements specification
        ├── plan.md     # Hierarchical task plan
        └── metadata.json

Read the full file on GitHub · 104 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 · 104 lines · 16 tokens per session scan A d3f37c128ac4

Subscribe to this mod's changes

help is a skill published in the GitHub repository MadAppGang/claude-code (279 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 726 once invoked, about $0.0001 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.