Conductor-Beads: Command for Claude Code

.claude/skills/conductor/references/commands/archive.md

archive is a command for Claude Code from NguyenSiTrung/Conductor-Beads. It costs 0 tokens per session (838 once invoked), scanned A, a copy of conductor-archive, Apache-2.0.

A command for moving completed Conductor tracks into an archive. A track is a documented piece of project work, and archiving removes it from the active track list while preserving its history.

In plain words
What is it for?
Use it to select completed tracks, extract reusable patterns and cautions, clean up stale parallel-work records, move track folders to conductor/archive/, and update tracks.md.
Why use it?
It reduces clutter in the active project and captures broadly useful lessons before completed work is moved away.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is NguyenSiTrung/Conductor-Beads's own configuration. It tells Claude Code how to work on Conductor-Beads itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Conductor-Beads configures →

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/archive.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.

agentmods badge for archive

README.md
[![agentmods](https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/archive/github.svg)](https://agentmods.dev/commands/nguyensitrung/conductor-beads/archive)
Your own site
<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/archive"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/archive/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.

agentmods 80×15 button for archive

Your own site · 80×15
<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/archive"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/archive.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 838 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00838
Opus 5 $0.00000 $0.00419
Sonnet 5 $0.00000 $0.00168
Haiku 4.5 $0.00000 $0.00084

Measured 9d ago against content hash 2430f1998b8a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

archive 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 9d 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-archive — 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/archive.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Conductor Archive

Archive completed tracks to clean up the project.

1. Find Completed Tracks

List all [x] tracks from tracks.md.

2. Select Tracks

  • Archive all completed
  • Or select specific ones
  • Or cancel

3. Archive Process

For each selected track:

  1. Create conductor/archive/ if needed
  2. Check for stale parallel state: If parallel_state.json exists, warn and clean up
  3. Extract learnings before archiving (see step 3a)
  4. Move track folder to archive
  5. Remove from tracks.md
  6. Add archive comment

3a. Extract Learnings Before Archiving

PROTOCOL: Preserve learnings from completed tracks (Ralph-style knowledge capture).

  1. Read Track Learnings: Load conductor/tracks/<track_id>/learnings.md

  2. Identify Patterns to Elevate:

    • Find patterns not yet in conductor/patterns.md
    • Find gotchas with general applicability
  3. Present Extraction Summary:

    "## Learnings from <track_id>"

    Patterns to preserve:

    Pattern Elevate to project?
    "Use X for Y"
    "Don't forget Z"

    "Select patterns to add to conductor/patterns.md (Enter numbers, 'all', or 'skip'):"

  4. Update Project Patterns:

    • Append selected patterns to conductor/patterns.md:
      - <pattern> (from: <track_id>, archived <date>)
      
  5. Preserve Learnings in Archive:

    • Keep learnings.md in the archived track folder
    • Future tracks can reference via /conductor-newtrack

4. Commit

Commit the archive operation.


5. BEADS COMPACTION

PROTOCOL: Compact Beads history for archived tracks.

  1. Check for Beads CLI:
    • Run which bd
    • If NOT found:

      "⚠️ Beads CLI (bd) is not installed. Beads provides persistent task memory across sessions." "A) Continue archive without Beads compaction" "B) Stop - I'll install Beads first"

      • If A: Skip this section
      • If B: HALT and wait for user

Read the full file on GitHub · 98 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.

  1. 9d ago First seen · 98 lines · 0 tokens per session scan A 2430f1998b8a

Subscribe to this mod's changes

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