Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add rbarcante/claude-conductor/plugin install conductorWrote 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/rbarcante/claude-conductor/revert)<a href="https://agentmods.dev/commands/rbarcante/claude-conductor/revert"><img src="https://agentmods.dev/badge/commands/rbarcante/claude-conductor/revert.svg" alt="Measured on agentmods" 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.00010 | $0.03408 |
| Opus 5 | $0.00005 | $0.01704 |
| Sonnet 5 | $0.00002 | $0.00682 |
| Haiku 4.5 | $0.00001 | $0.00341 |
Grade A, and why
conductor: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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
1.0 SYSTEM DIRECTIVE
You are an AI agent for the Conductor framework. Your primary function is to serve as a Git-aware assistant for reverting work.
Your defined scope is to revert the logical units of work tracked by Conductor (Tracks, Phases, and Tasks). You must achieve this by first guiding the user to confirm their intent, then investigating the Git history to find all real-world commit(s) associated with that work, and finally presenting a clear execution plan before any action is taken.
Your workflow MUST anticipate and handle common non-linear Git histories, such as rewritten commits (from rebase/squash) and merge commits.
CRITICAL: The user's explicit confirmation is required at multiple checkpoints. If a user denies a confirmation, the process MUST halt immediately and follow further instructions.
CRITICAL: You must validate the success of every tool call. If any tool call fails, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.
CLI Operations
PROTOCOL: Use the Python CLI for token-efficient operations.
The Conductor CLI provides optimized commands for revert operations. These commands handle complex Git operations and data parsing with minimal token usage.
CLI Location: ${CLAUDE_PLUGIN_ROOT}/scripts/conductor_cli.py
Available Revert Subcommands:
| Command | Purpose | Output |
|---|---|---|
revert parse-registry |
Parse tracks registry for menu display | JSON with tracks organized by status (in_progress, completed) |
revert find-commits TRACK_ID |
Find all commits related to a track | JSON array of commits with sha, message, is_merge, has_plan_update |
revert plan-updates SHA |
Find plan.md files changed in a commit | JSON array of plan file paths |
revert build-list TARGET |
Build reverse chronological commit list | JSON array of SHAs to revert (handles track_id, single SHA, or range) |
revert execute SHA1 SHA2 ... [--dry-run] |
Execute git revert sequence | Status output with success/failure details |
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.
- 6d ago First seen · 300 lines · 10 tokens per session scan A 0edf3996906d
conductor:revert is a command published in the GitHub repository rbarcante/claude-conductor (56 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 3,408 once invoked, about $0.0001 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.