agentmods.dev

create-conductor-flow: Instructions file for Claude Code

CLAUDE.md

create-conductor-flow CLAUDE.md is an instructions file for Claude Code from Jonkimi/create-conductor-flow. It costs 533 tokens per session, scanned A, a copy of Conductor-for-all AGENTS.md, Apache-2.0.

Instructions for using Conductor, a project-planning extension, and for finding its project and track files. A track is a separate planned piece of work within a project.

In plain words
What is it for?
Use it when working with Conductor plans, tracks, indexes, product definitions, or other files referenced through the project's file structure.
Why use it?
It helps an AI agent locate the right plans and context instead of guessing which files contain the requested information.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

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

not rated 5repo 7mo ago A scan 533 tokens copy · 100% Apache-2.0
View source ↗ Jonkimi/create-conductor-flow npmjs.com
Reuse

Borrowing it

Nothing to install: this file belongs to Jonkimi/create-conductor-flow. 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/Jonkimi/create-conductor-flow/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/Jonkimi/create-conductor-flow

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 create-conductor-flow CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jonkimi/create-conductor-flow/claude-md/github.svg)](https://agentmods.dev/instructions/jonkimi/create-conductor-flow/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/jonkimi/create-conductor-flow/claude-md"><img src="https://agentmods.dev/badge/instructions/jonkimi/create-conductor-flow/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 create-conductor-flow CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/jonkimi/create-conductor-flow/claude-md"><img src="https://agentmods.dev/badge/instructions/jonkimi/create-conductor-flow/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 533 This file is loaded in full into every session.
When invoked 533 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 100% copy Near-identical to another mod 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.00533 $0.00533
Opus 5.5 $0.00213 $0.00213
Sonnet 5.5 $0.00107 $0.00107
Haiku 4.5 $0.00053 $0.00053

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

Security

Grade A, and why

create-conductor-flow 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.

Origin

This is a copy

100% identical to Conductor-for-all AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

CLAUDE.md · 42 lines

How it starts

The opening of the file, as written. The whole thing — 42 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 conductor extension in the current session, they are likely referring to the conductor/tracks.md file or 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):

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

  2. Check Index: Read the index file and look for a link with a matching or semantically similar label.

  3. Resolve Path: If a link is found, resolve its path relative to the directory containing the index.md file.

    • Example: If conductor/index.md links to ./workflow.md, the full path is conductor/workflow.md.

  4. Fallback: If the index file is missing or the link is absent, use the Default Path keys below.

  5. 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 Registry: conductor/tracks.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

Read the full file on GitHub · 42 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 First seen · 42 lines · 533 tokens per session scan A fda48c016552

Subscribe to this mod's changes

create-conductor-flow CLAUDE.md is an instructions file published in the GitHub repository Jonkimi/create-conductor-flow (5 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 533 tokens to every session, about $0.0021 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to Conductor-for-all AGENTS.md, differing in 0 lines, and is treated as a copy.

Claude CodePlanningagent-workflowantigravityconductorcontext-driven-developmentfactory-droid
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

vscode model-prompts.instructions.md

Model-specific prompt authoring and registry guidelines.

microsoft/vscode · 2,022 tokens