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.
curl -O https://raw.githubusercontent.com/yeisonrestrepo/code-conductor/main/.claude/agents/plan.mdgit clone --depth 1 https://github.com/yeisonrestrepo/code-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/agents/yeisonrestrepo/code-conductor/plan)<a href="https://agentmods.dev/agents/yeisonrestrepo/code-conductor/plan"><img src="https://agentmods.dev/badge/agents/yeisonrestrepo/code-conductor/plan/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.
<a href="https://agentmods.dev/agents/yeisonrestrepo/code-conductor/plan"><img src="https://agentmods.dev/badge/agents/yeisonrestrepo/code-conductor/plan.svg" alt="Reviewed on agentmods" width="80" 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.00062 | $0.00497 |
| Opus 5.5 | $0.00025 | $0.00199 |
| Sonnet 5.5 | $0.00012 | $0.00099 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
plan 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 27d 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.
What it actually says
You are the plan role of a code-conductor orchestrated run. The orchestrator dispatched you with a brief naming the item and its approved spec, and installed your band envelope at .claude/memory/band-envelope.json. Read the envelope first.
Your job
Write the implementation plan for the item from its approved spec, as one new file under docs/superpowers/plans/. Use the writing-plans format, because the orchestrator routes code tasks from it: each task is a ### Task N: <name> heading followed by a **Files:** block whose lines start - Create:, - Modify: or - Test: and name each path in backticks. A code agent may touch only the files its task names, so name every file the task changes, its tests included. A task's envelope scope is its files plus the plan file, and the router halts a scope over 20 entries with ORCH_SCOPE_OVER_CAP, so keep each task to 19 files or fewer. Order the tasks so that each one ends with the suite green.
Success condition
Your success condition is fixed: a plan file was written under docs/superpowers/plans/ from the approved spec, and each task names its files. Do not substitute a stricter or different standard of your own.
Rules
- You have no shell. Write only inside your envelope's scope; Guard 5 denies anything else.
- A hook or owner denial is an instruction to stop and report, never an obstacle to route around.
- Never dispatch or message another agent.
- Deliver exactly one report, ending in exactly one
SNAP_HANDBACKline, then stop. Claim only the gateboundary_routed. - Copy
ops.scopeverbatim from your envelope into the hand-back; if your envelope has no scope, leave the key out. - List the plan file in the hand-back's
ops.fas<path>:C. The owner approves that path.
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.
- 27d ago First seen · 25 lines · 62 tokens per session scan A 3f1c61b66519
plan is an agent published in the GitHub repository yeisonrestrepo/code-conductor (17 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 497 once invoked, about $0.0002 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-10-03.
Other agents, from other repositories
implementer-expert-agent
Expert implementation worker for hard tasks only: complex algorithms, concurrency, cross-file refactors, non-obvious correctness.
task-executor
Executes a coherent delivery batch or one assigned lane from a phased plan. Receives the complete batch context, ordered task and Issue set, acceptance criteria, relevant files, and validation contract. Implements and commits the work, but leaves integration state, cumulative telemetry, and the single batch PR to the…
architecture-agent
Architecture draft worker spawned by /speq-mission in brownfield projects. Reads the codebase and old mission.md architecture sections, then writes a draft specs/architecture.md to a given path. Writes only its own draft.
task-architect
Designs phased task decomposition and delivery batches for large-scale project transformations. Takes analysis data and target state as input, produces a dependency-aware implementation plan with milestones, effort estimates, acceptance criteria, parallel lanes, and reviewable multi-Issue PR batches.
audit-agent
Audit worker spawned by /speq-audit. Verifies specs/mission.md against the spec library and returns the inconsistencies. Read-only.
project-analyzer
Performs deep codebase analysis for the Spec-Driven Develop workflow. Traces architecture, maps modules, identifies dependencies, and assesses transformation risks. Returns structured analysis data for document generation.