Conductor-Beads: Command for Claude Code

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

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

A command for creating temporary exploration tracks in a Conductor project, using Beads to record short-lived work outside Git synchronization.

In plain words
What is it for?
Use it for exploratory approaches, debugging sessions, quick fixes, patrol cycles, and health checks that do not need a lasting audit trail.
Why use it?
It keeps experiments, quick debugging, and routine checks from adding permanent task history. It requires the Beads command-line tool and an initialized Beads project.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/wisp"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/wisp.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,479 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 89% 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.01479
Opus 5 $0.00000 $0.00740
Sonnet 5 $0.00000 $0.00296
Haiku 4.5 $0.00000 $0.00148

Measured 5d ago against content hash 33ba11463ff9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

wisp 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 5d 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

89% identical to conductor-wisp — 12 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/wisp.md · 215 lines

How it starts

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

Conductor Wisp

Create ephemeral exploration track: $ARGUMENTS


1.0 BEADS CHECK

PROTOCOL: Verify Beads is available.

  1. Check Beads CLI: Run which bd

  2. Check Beads Initialization:

    • If .beads/ directory does NOT exist:

      "⚠️ Beads is not initialized in this project." "Run bd init first, or use /conductor-setup to set up the project."

      • HALT

2.0 UNDERSTAND WISPS

PROTOCOL: Explain ephemeral exploration tracks.

Wisps are ephemeral workflow instances that:

  • Live in Dolt wisps table (excluded from sync via dolt_ignore)
  • Are never synced to git
  • Leave no permanent audit trail
  • Perfect for exploration, debugging, quick fixes

Use wisps when:

  • Exploring an approach before committing to it
  • Quick debugging session
  • Temporary work that shouldn't clutter history
  • Patrol cycles, health checks, routine monitoring

Use persistent tracks (bd mol pour) when:

  • Feature development
  • Bug fixes that need audit trail
  • Work spanning multiple sessions
  • Team coordination required

3.0 CREATE WISP

PROTOCOL: Create ephemeral exploration track.

3.1 Parse Arguments

If formula name provided:

  • Use the specified formula
  • Extract any --var key=value arguments

If no formula name:

  1. List Available Formulas:

    bd formula list --json
    
  2. If formulas exist:

    "Available formulas for ephemeral exploration:"

    # Formula Description
    1 <name> <desc>

    "Enter formula number or name, or describe what you want to explore:"

  3. If no formulas:

    "No formulas found. Creating ad-hoc exploration wisp." "What do you want to explore? (Describe briefly)"

    • Wait for user input
    • Go to section 3.3 (Ad-hoc Wisp)

3.2 Create Wisp from Formula

Read the full file on GitHub · 215 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. 5d ago First seen · 215 lines · 0 tokens per session scan A 33ba11463ff9

Subscribe to this mod's changes

wisp 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 1,479 tokens. A static security scan graded it A with 0 findings. It is 89% identical to conductor-wisp, differing in 12 lines, and is treated as a copy.