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.
npx agentmods add instructions/jonkimi/create-conductor-flow/gemini-mdgit clone --depth 1 https://github.com/Jonkimi/create-conductor-flowWhat 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 | $0.00533 | $0.00533 |
| Opus 5 | $0.00267 | $0.00267 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
create-conductor-flow GEMINI.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.
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.
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):
-
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 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
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.
- 2d ago First seen · 42 lines · 533 tokens per session scan A fda48c016552
create-conductor-flow GEMINI.md is an instructions file published in the GitHub repository Jonkimi/create-conductor-flow (5 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 533 tokens to every session, about $0.0027 per session on Opus 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.
Other instructions, from other repositories
passdown AGENTS.md
Instructions for vunm-io/passdown, covering agents.md — passdown, what this repo is, branch policy, before committing a change here and release rule.
Conductor-for-all AGENTS.md
Instructions for hlhr202/Conductor-for-all, covering conductor context and universal file resolution protocol.
Conductor-for-all CLAUDE.md
Instructions for hlhr202/Conductor-for-all, covering conductor context and universal file resolution protocol.
three-man-team CLAUDE.md
Instructions for russelleNVy/three-man-team, covering three man team — session router, token rules — always active, session start — every role and reference files — on demand only.
toh-framework CLAUDE.md
Instructions for wasintoh/toh-framework, covering claude.md — toh framework (repo development guide), what this is, everyday commands, verification protocol and single source, transformed per ide.
awesome-copilot-id AGENTS.md
Instructions for GulajavaMinistudio/awesome-copilot-id, covering communication, explanation and documentation, markdown formatting, user communication style and workflow & methodology.