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.
npx skills add agent-skills-hub/agent-skills-hub --skill conductor-revertgit clone --depth 1 https://github.com/agent-skills-hub/agent-skills-hubWrote 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/skills/agent-skills-hub/agent-skills-hub/conductor-revert)<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.
<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>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.00020 | $0.02183 |
| Opus 5 | $0.00010 | $0.01092 |
| Sonnet 5 | $0.00004 | $0.00437 |
| Haiku 4.5 | $0.00002 | $0.00218 |
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 9d 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
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.
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
-
Verify Conductor is initialized:
- Check
conductor/tracks.mdexists - If missing: Display error and suggest running
/conductor:setupfirst
- Check
-
Verify git repository:
-
Run
git statusto 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
-
-
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:
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.
- 9d ago First seen · 373 lines · 20 tokens per session scan A 78985f54abea
conductor-revert is a skill published in the GitHub repository agent-skills-hub/agent-skills-hub (96 stars, last pushed 18d ago), licensed MIT. It adds 20 tokens to every session and 2,183 once invoked, about $0.0001 per session on Opus 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.
Other skills, from other repositories
intuitive-squash
Squash local GSD or agent-generated commit history into a clean, reviewable story while preserving important fixes. Use when the user asks to squash commits, clean git history, compress phase commits, prepare a branch before PR, compare aggressive vs moderate squash options, or preserve hotfix/security commits during…
ox-cli-pr-header
Emit and paste the SageOx credit line at the TOP of a pull-request description — the human-facing counterpart to the machine SageOx-Session: trailer. Run ox pr header at PR-creation time; it renders a thin, on-brand, dark/light-aware single line linking the session(s), plan(s), and discussion(s) that produced the…
worktree-assign
A worktree assignment guide for creating a Git worktree and sending a coding task to an AI agent. A worktree is a separate working directory that lets a branch be worked on independently.
project-flow-ops
CIEL's coordination layer for triaging issues, PRs, and tasks across GitHub and internal tracking systems (e.g., Linear).
commit
Creates conventional git commits enriched with a Context section that logs AI-layer changes (.wisci/, CLAUDE.md, skills, rules), turning git history into queryable long-term memory. Use to commit changes, optionally pushing afterward.
dev-updates
Detect and summarize uncommitted git changes grouped by feature area, then generate a structured commit message. Use when the user says "what's the update?", "what changed?", "summarize my changes", "what have I done?", or "what did I update?".