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-block.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-block)<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/conductor-block"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/conductor-block/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-block"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/conductor-block.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.00431 |
| Opus 5 | $0.00004 | $0.00216 |
| Sonnet 5 | $0.00002 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
conductor-block 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:
- block — 88% identical, 4 lines differ
What it actually says
Conductor Block
Mark a task as blocked.
1. Identify Task
- If argument provided, find that task
- Otherwise show in-progress tasks for selection
2. Get Reason
Ask for the blocking reason.
3. Update Plan
Change [~] to [!] and append [BLOCKED: reason]
4. Beads Sync
PROTOCOL: Sync block action with Beads.
-
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 without Beads sync" "B) Stop - I'll install Beads first"- If A: Skip to step 5
- If B: HALT and wait for user
- Run
-
Sync Block Action (if task has
beads_task_idin track metadata):- Run:
bd update <task_id> --status blocked bd update <task_id> --notes "BLOCKED: <reason> CATEGORY: <External/Technical/Resource> WAITING FOR: <what needs to happen to unblock> DISCOVERED: <if blocking issue is new, create with discovered-from>" - If blocker is another task, create dependency:
bd dep add <blocked_task> <blocker_task> - If any
bdcommand fails:"⚠️ Beads command failed: " "A) Continue without Beads sync" "B) Retry the failed command" "C) Stop - I'll fix the issue first"
- If A: Skip remaining Beads steps
- If B: Retry the command
- If C: HALT and wait for user
- Run:
5. Confirm
Announce task is blocked.
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 · 53 lines · 8 tokens per session scan A e84ab32474b9
conductor-block 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 431 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.