conductor-revert

conductor-revert is a skill for Claude Code, Codex from agent-skills-hub/agent-skills-hub. It costs 20 tokens per session (2,183 once invoked), scanned A, a copy of conductor-revert, MIT.

A Git-aware undo guide for Conductor work, where Git is the version-control system that records code changes. It can target a whole track, a phase, or an individual task.

In plain words
What is it for?
Use it to revert a Conductor track, phase, or task after reviewing the repository state.
Why use it?
It helps undo a defined unit of work while checking the repository and warning about uncommitted changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to revert a Conductor track, phase, or task after reviewing the repository state.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/agent-skills-hub/agent-skills-hub/conductor-revert
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add agent-skills-hub/agent-skills-hub --skill conductor-revert
Clone the repo
git clone --depth 1 https://github.com/agent-skills-hub/agent-skills-hub

Made for: Claude Code, Codex.

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 conductor-revert

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

agentmods 80×15 button for conductor-revert

Your own site · 80×15
<a href="https://agentmods.dev/skills/agent-skills-hub/agent-skills-hub/conductor-revert"><img src="https://agentmods.dev/badge/skills/agent-skills-hub/agent-skills-hub/conductor-revert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,183 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 97% 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.00020 $0.02183
Opus 5.5 $0.00008 $0.00873
Sonnet 5.5 $0.00004 $0.00437
Haiku 4.5 $0.00002 $0.00218

Measured 1mo ago against content hash 78985f54abea, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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

97% identical to conductor-revert — 1 line 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.

skills/conductor-revert/SKILL.md · 373 lines

How it starts

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

Revert Track

Revert changes by logical work unit with full git awareness. Supports reverting entire tracks, specific phases, or individual tasks.

Use this skill when

  • Working on revert track tasks or workflows
  • Needing guidance, best practices, or checklists for revert track

Do not use this skill when

  • The task is unrelated to revert track
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.
  • If detailed examples are required, open resources/implementation-playbook.md.

Pre-flight Checks

  1. Verify Conductor is initialized:

    • Check conductor/tracks.md exists
    • If missing: Display error and suggest running /conductor:setup first
  2. Verify git repository:

    • Run git status to confirm git repo

    • Check for uncommitted changes

    • If uncommitted changes exist:

      WARNING: Uncommitted changes detected
      
      Files with changes:
      {list of files}
      
      Options:
      1. Stash changes and continue
      2. Commit changes first
      3. Cancel revert
      
  3. Verify git is clean enough to revert:

    • No merge in progress
    • No rebase in progress
    • If issues found: Halt and explain resolution steps

Target Selection

If argument provided:

Parse the argument format:

Full track: {trackId}

  • Example: auth_20250115
  • Reverts all commits for the entire track

Specific phase: {trackId}:phase{N}

  • Example: auth_20250115:phase2
  • Reverts commits for phase N and all subsequent phases

Specific task: {trackId}:task{X.Y}

  • Example: auth_20250115:task2.3
  • Reverts commits for task X.Y only

If no argument:

Display guided selection menu:

What would you like to revert?

Currently In Progress:
1. [~] Task 2.3 in dashboard_20250112 (most recent)

Recently Completed:
2. [x] Task 2.2 in dashboard_20250112 (1 hour ago)
3. [x] Phase 1 in dashboard_20250112 (3 hours ago)
4. [x] Full track: auth_20250115 (yesterday)

Options:
5. Enter specific reference (track:phase or track:task)
6. Cancel

Select option:

Read the full file on GitHub · 373 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. 1mo ago First seen · 373 lines · 20 tokens per session scan A 78985f54abea

Subscribe to this mod's changes

conductor-revert is a skill published in the GitHub repository agent-skills-hub/agent-skills-hub (124 stars, last pushed 26d ago), licensed MIT. It adds 20 tokens to every session and 2,183 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to conductor-revert, differing in 1 line, and is treated as a copy.

Related

Other skills, from other repositories

friction-log

File contributor or agent papercuts as GitHub issues labeled friction, or investigate those issues as the daily friction-log Cloud Agent. Use when you hit repo friction, when asked to log friction, or when spawned to resolve open friction issues.

educlopez/ui-craft · 52 tokens

split-and-ship

Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".

tobihagemann/turbo · 61 tokens

git-issue-start

Take a GitHub issue from open to a checked-out branch - assign it to you, mark it in progress if the repo has such a label, derive a conventional branch name from its type: label, branch off the detected base. Use for "start issue 42", "work on #42", "/git-issue-start 42", "let's do 42", "pick up that issue", "take…

pivoshenko/pivoshenko.ai · 174 tokens

github-issue

Use when opening a GitHub issue, bug report, feature request, or discussion in any repository, including one the user has no local checkout of.

LandonSchropp/agent-toolkit · 30 tokens

git-edit-commit

Use when needing to fixup, squash, drop, reword, reorder, or edit commits in a branch's history. Handles the non-interactive approach agents need since git rebase -i requires a TTY.

LandonSchropp/agent-toolkit · 51 tokens

loopit

Drive a task queue (loop-tasks.md) to completion in ANY repo. Detect the repo's own rules, then for each task plan -> /review-plan -> implement -> verify -> /review -> fix all findings -> /battle-test -> commit -> push -> client doc -> mark done. Each task runs in its OWN subagent (context isolation, token-cheap); the…

Jewgah/claude-code-skills · 95 tokens