A command that compares a project's current code with its Conductor documentation and updates the documents to match. It can refresh technical, product, workflow, or individual track information.

Keeping Conductor context files in sync with the codebase, reviewing documentation drift, backing up changed files, recording refresh state, and committing the updates.

Project documentation can become outdated as dependencies, completed work, and development tools change. This command shows those differences and asks for approval before updating the files.

How NguyenSiTrung/Conductor-Beads configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/NguyenSiTrung/Conductor-Beads/main/.claude/skills/conductor/references/commands/refresh.md

Clone the repo

git clone --depth 1 https://github.com/NguyenSiTrung/Conductor-Beads

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/refresh/github.svg)](https://agentmods.dev/commands/nguyensitrung/conductor-beads/refresh)

Your own site

<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/refresh"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/refresh"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/refresh.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,023 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 97% copy Near-identical to another mod in the catalogue.

Token cost

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.00000	$0.01023
Opus 5.5	$0.00000	$0.00409
Sonnet 5.5	$0.00000	$0.00205
Haiku 4.5	$0.00000	$0.00102

Measured 2mo ago against content hash ee1653e67763, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 2mo 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.

Origin

This is a copy

97% identical to conductor-refresh — 4 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.

.claude/skills/conductor/references/commands/refresh.md · 142 lines

How it starts

The opening of the file, as written. The whole thing — 142 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 refresh
tech - tech-stack.md only
product - product.md only
workflow - workflow.md only
track [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.md from all tracks in conductor/tracks/*/
- Read learnings.md from all archived tracks in conductor/archive/*/
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)"

Pattern	Tracks	Already in patterns.md?
"Use Zod for validation"	auth, api, users	❌ No
"Barrel exports required"	auth, config	✅ Yes

Read the full file on GitHub · 142 lines

Changes

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.

2mo ago First seen · 142 lines · 0 tokens per session scan A ee1653e67763

Subscribe to this mod's changes

refresh is a command published in the GitHub repository NguyenSiTrung/Conductor-Beads (23 stars, last pushed 8mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,023 tokens. A static security scan graded it A with 0 findings. It is 97% identical to conductor-refresh, differing in 4 lines, and is treated as a copy.

Writing and docs

refresh next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
refreshNguyenSiTrung/Conductor-Beads	Command	23	8mo ago	Apache-2.0	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

Conductor-Beads: Command for Claude Code