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.
git clone --depth 1 https://github.com/Jinghao67/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/commands/jinghao67/conductor/cd-complete)<a href="https://agentmods.dev/commands/jinghao67/conductor/cd-complete"><img src="https://agentmods.dev/badge/commands/jinghao67/conductor/cd-complete/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/commands/jinghao67/conductor/cd-complete"><img src="https://agentmods.dev/badge/commands/jinghao67/conductor/cd-complete.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.00019 | $0.00364 |
| Opus 5.5 | $0.00008 | $0.00146 |
| Sonnet 5.5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
cd-complete 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.
What it actually says
Branch + brief (resolved from this session's binding):
!SID="${CLAUDE_SESSION_ID}"; B="$(jq -r '.branch_id // empty' ".conductor/bindings/$SID.json" 2>/dev/null)"; if [ -z "$B" ]; then echo "This session is not bound to a branch. Run /cd-bind <id> first."; else echo "branch=$B"; echo "--- brief ---"; cat ".conductor/branches/$B/brief.md" 2>/dev/null; fi; true
Only proceed if the user has confirmed this branch is complete (a branch may suggest completion, but only the user confirms it).
Write .conductor/branches/<branch-id>/completion-report.md (your own branch dir — allowed) using this structure. Keep the Suggested Merge Note ≤150 words — it is the only text intended for the master context:
# Completion Report: <branch-id> — <title>
## Result
3–6 sentences on the outcome.
## Artifacts / Files
- paths produced or changed
## Decisions Made Locally
- ...
## Proposed Global Decisions
- Decision / Scope affected / Why it matters / Branches affected / Recommended master action
## Validation / Checks
- what you ran/verified
## Risks
- ...
## Suggested Merge Note
<=150 words. The compressed, master-ready summary.
Writing this report flips the branch to report_ready automatically. Tell the user to run /cd-merge <branch-id> from the master session to fold the result in.
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.
- 1mo ago First seen · 39 lines · 19 tokens per session scan A 5b459aa31ba6
cd-complete is a command published in the GitHub repository Jinghao67/conductor (99 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 364 once invoked, about $0.0001 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.