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/skills/conductor/references/commands/revert.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/revert)<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/revert"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/revert/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/revert"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/revert.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.00000 | $0.01893 |
| Opus 5 | $0.00000 | $0.00946 |
| Sonnet 5 | $0.00000 | $0.00379 |
| Haiku 4.5 | $0.00000 | $0.00189 |
Grade A, and why
revert 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.
This is a copy
92% identical to conductor-revert — 11 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.
How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conductor Revert
Revert Conductor work: $ARGUMENTS
Scope: Revert logical units of work tracked by Conductor (Tracks, Phases, Tasks) by investigating Git history and finding all associated commits.
1.0 SETUP CHECK
PROTOCOL: Verify project is properly set up before proceeding.
-
Verify Tracks File: Check if
conductor/tracks.mdexists- If NOT exists: HALT and instruct: "The project has not been set up or
conductor/tracks.mdis corrupted. Please run/conductor-setupor restore the file."
- If NOT exists: HALT and instruct: "The project has not been set up or
-
Verify Track Content: Check if
conductor/tracks.mdis not empty- If empty: HALT with same message as above
2.0 PHASE 1: INTERACTIVE TARGET SELECTION & CONFIRMATION
GOAL: Guide user to clearly identify and confirm the logical unit to revert before analysis begins.
-
Initiate Revert Process: Determine user's target.
-
Check for User-Provided Target:
- IF target provided (e.g.,
/conductor-revert track <track_id>): → PATH A: Direct Confirmation - IF NO target provided: → PATH B: Guided Selection Menu (default)
- IF target provided (e.g.,
-
Interaction Paths:
PATH A: Direct Confirmation
- Find the specific track, phase, or task in
tracks.mdor relevantplan.md - Ask for confirmation:
"You asked to revert the [Track/Phase/Task]: '[Description]'. Is this correct?" A) Yes B) No
- If "Yes": Establish as
target_intent→ Proceed to Phase 2 - If "No": Ask clarifying questions to find correct item
PATH B: Guided Selection Menu
-
Identify Revert Candidates:
- Scan All Plans: Read
conductor/tracks.mdAND everyconductor/tracks/*/plan.md - Prioritize In-Progress: Find ALL Tracks, Phases, Tasks marked
[~] - Fallback to Completed: If NO in-progress items found, find 5 most recently completed (
[x])
- Scan All Plans: Read
-
Present Unified Hierarchical Menu:
Example when in-progress items found:
"I found multiple in-progress items. Please choose which to revert:"
Track: track_20251208_user_profile
-
[Phase] Implement Backend API
-
[Task] Update user model
-
A different Track, Task, or Phase.
-
- Find the specific track, phase, or task in
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 · 197 lines · 0 tokens per session scan A 3c9983d87955
revert 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,893 tokens. A static security scan graded it A with 0 findings. It is 92% identical to conductor-revert, differing in 11 lines, and is treated as a copy.
Other commands, from other repositories
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.