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 commands/liortesta/clawdagent/conductorgit clone --depth 1 https://github.com/liortesta/ClawdAgentWhat 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.00000 | $0.00666 |
| Opus 5 | $0.00000 | $0.00333 |
| Sonnet 5 | $0.00000 | $0.00133 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
conductor 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conductor Workflow — Structured Development Flow
A structured, phase-based development workflow from product vision to deployed feature. Like a symphony conductor — each instrument plays at the right time.
Phases:
Phase 1: CONTEXT (Understanding)
- Read ALL relevant code, docs, and requirements
- Identify existing patterns, utilities, and components to reuse
- Map the dependency graph of affected modules
- List unknowns and assumptions
- Output: Context Document
Phase 2: SPEC & PLAN (Architecture)
Use CTO + Architect agents:
- Define the feature scope (what's in / what's out)
- Write technical specification:
- Data model changes
- API contract (endpoints, request/response)
- UI components needed
- Integration points
- Break into development tracks:
Track A: Backend (API + DB) Track B: Frontend (UI + State) Track C: Infrastructure (CI/CD + Config) - Define milestones and checkpoints
- Output: Technical Spec + Task Board
Phase 3: IMPLEMENT (Track-Based)
Execute tracks in parallel where possible:
-
Track A: Backend
- DB migrations / schema changes
- Data access layer
- Business logic
- API endpoints
- Backend tests
-
Track B: Frontend
- Component structure
- State management
- API integration
- UI polish
- Frontend tests
-
Track C: Infrastructure
- Environment config
- CI/CD updates
- Monitoring/logging
- Documentation
Each track has its own QA checkpoint.
Phase 4: INTEGRATE (Merge & Test)
- Merge all tracks
- Run integration tests
- Run E2E tests
- Visual verification (/visual-verify)
- Performance check
Phase 5: VALIDATE (Quality Gates)
- Run /ship to check all quality gates
- Security audit on complete feature
- Code review with fresh eyes
- Documentation is complete
Phase 6: DELIVER
- Create PR with comprehensive description
- Link to related issues
- Tag reviewers
- Run /wrap-up to update project memory
Output Format:
## Conductor Report — [Feature Name]
### Phase Status
| Phase | Status | Duration |
|-------|--------|----------|
| Context | DONE | ~X min |
| Spec & Plan | DONE | ~X min |
| Track A: Backend | DONE | ~X min |
| Track B: Frontend | DONE | ~X min |
| Track C: Infra | DONE | ~X min |
| Integration | DONE | ~X min |
| Validation | DONE | ~X min |
### Deliverables
- [X] Technical spec
- [X] Implementation (Y files changed)
- [X] Tests (X unit, Y integration, Z E2E)
- [X] Documentation updated
- [X] PR created: #XXX
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.
- 3d ago First seen · 103 lines · 0 tokens per session scan A 3ae76c67a44b
conductor is a command published in the GitHub repository liortesta/ClawdAgent (11 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 666 tokens. 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.