Borrowing it
Nothing to install: this file belongs to NguyenSiTrung/Conductor-Beads. 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/NguyenSiTrung/Conductor-Beads/main/.claude/commands/conductor-refresh.mdgit clone --depth 1 https://github.com/NguyenSiTrung/Conductor-BeadsWrote 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/nguyensitrung/conductor-beads/conductor-refresh)<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/conductor-refresh"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/conductor-refresh/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/nguyensitrung/conductor-beads/conductor-refresh"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/conductor-refresh.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.00008 | $0.01036 |
| Opus 5 | $0.00004 | $0.00518 |
| Sonnet 5 | $0.00002 | $0.00207 |
| Haiku 4.5 | $0.00001 | $0.00104 |
Grade A, and why
conductor-refresh 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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- refresh — 97% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conductor Refresh
Sync conductor context documentation with the current codebase state.
1. Verify Setup
Check conductor/ exists with core files. If not, suggest /conductor-setup.
2. Determine Scope
If no argument, ask:
all- Full refreshtech- tech-stack.md onlyproduct- product.md onlyworkflow- workflow.md onlytrack [id]- Specific track
3. Analyze Drift
Compare current codebase against docs:
- Tech: Scan package.json, requirements.txt, etc. for new/removed deps
- Product: Check completed tracks not reflected in product.md
- Workflow: Check CI/CD changes, new tooling
4. Present Drift Report
Show what's changed since last setup/refresh.
5. Confirm Updates
Ask user to approve changes.
6. Apply Updates
- Create backups (*.md.bak)
- Update files with new information
- Add refresh marker to top of files
7. Update State
Create/update conductor/refresh_state.json with timestamp and changes.
8. Commit
git add conductor/
git commit -m "conductor(refresh): Sync context with codebase"
8a. CONSOLIDATE LEARNINGS (Pattern Flywheel)
PROTOCOL: Aggregate and consolidate learnings across all tracks into project patterns.
-
Scan All Track Learnings:
- Read
learnings.mdfrom all tracks inconductor/tracks/*/ - Read
learnings.mdfrom all archived tracks inconductor/archive/*/
- Read
-
Extract Pattern Candidates:
- Find patterns mentioned 2+ times across different tracks
- Find gotchas that reoccur
- Find context that applies project-wide
-
Present Consolidation Report:
"## Learnings Consolidation Report"
Patterns found across tracks:
Pattern Tracks Already in patterns.md? "Use Zod for validation" auth, api, users ❌ No "Barrel exports required" auth, config ✅ Yes New patterns to add: [list] Duplicate patterns to merge: [list]
"Would you like to update
conductor/patterns.md? (yes/no)"
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.
- 10d ago First seen · 146 lines · 8 tokens per session scan A 93fe6d6bcf6e
conductor-refresh is a command published in the GitHub repository NguyenSiTrung/Conductor-Beads (24 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 1,036 once invoked, about $0.0000 per session on Opus 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.