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-skip.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-skip)<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/conductor-skip"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/conductor-skip/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-skip"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/conductor-skip.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.00007 | $0.00501 |
| Opus 5 | $0.00003 | $0.00251 |
| Sonnet 5 | $0.00001 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
conductor-skip 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:
- skip — 97% identical, 4 lines differ
What it actually says
Conductor Skip
Skip the current in-progress task.
1. Find Current Task
- Find in-progress track in
tracks.md - Find in-progress task in that track's
plan.md
2. Get Reason
Ask why skipping:
- Will complete later
- No longer needed
- Blocked by external factor
- Other
3. Update Plan
- If "no longer needed": Mark as
[x] (SKIPPED) - Otherwise: Reset to
[ ]with skip comment - Mark next pending task as
[~]
4. Update State
Update implement_state.json with new task index.
5. Announce
Confirm skip and show next task.
6. BEADS SYNC
PROTOCOL: Sync skip 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 this section
- If B: HALT and wait for user
- Run
-
Sync Skip Actions:
- "No longer needed":
bd close <task_id> --reason "Skipped: <reason>" - "Will complete later":
bd update <task_id> --status open bd update <task_id> --notes "SKIPPED: <reason>. Will complete later." - "Blocked":
bd update <task_id> --status blocked --notes "SKIPPED: <reason>" - 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
- "No longer needed":
-
Update next task:
bd update <next_task_id> --status in_progress --assignee conductor
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 · 64 lines · 7 tokens per session scan A 30d40ec9e284
conductor-skip is a command published in the GitHub repository NguyenSiTrung/Conductor-Beads (24 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 501 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.