Conductor-Beads: Command for Claude Code

.claude/skills/beads/commands/restore.md

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

A read-only command for recovering the complete history of an issue from Git after its details were compacted. It uses the saved commit to show the issue as it existed then, including its description and events.

In plain words
What is it for?
Use it to review old issues, recover forgotten details, investigate past decisions, or create an audit trail.
Why use it?
It brings back context that may no longer be visible in the current issue, without changing the database or Git files.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

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/beads/commands/restore.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 restore

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/restore"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/restore.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 159 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 100% 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.00009 $0.00159
Opus 5 $0.00005 $0.00079
Sonnet 5 $0.00002 $0.00032
Haiku 4.5 $0.00001 $0.00016

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

Security

Grade A, and why

restore 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

100% identical to restore — 2 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/beads/commands/restore.md · 28 lines

What it actually says

Restore full history of a compacted issue from git version control.

When an issue is compacted, the git commit hash is saved. This command:

  1. Reads the compacted_at_commit from the database
  2. Retrieves the full issue from Dolt history at that point
  3. Displays the full issue history (description, events, etc.)
  4. Returns to the current state

Usage

bd restore bd-42

This is read-only - it does not modify the database or git state.

Useful for:

  • Reviewing old issues after compaction
  • Recovering forgotten context
  • Audit trails
  • Historical research

Requires git repository with issue history.

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 · 28 lines · 9 tokens per session scan A 8cda7ebcaa57

Subscribe to this mod's changes

restore is a command published in the GitHub repository NguyenSiTrung/Conductor-Beads (24 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 159 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to restore, differing in 2 lines, and is treated as a copy.