crew-rollback

A command that undoes the file changes from the most recent task using Git, a system for tracking code changes.

In plain words
What is it for?
Use it to inspect the last task's affected files, confirm the reversal, restore those changes, and update the code index.
Why use it?
It provides a way to reverse a task after reviewing which files it changed.

Command

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.

agentmods
npx agentmods add commands/d3x293/code-crew/crew-rollback
Clone the repo
git clone --depth 1 https://github.com/d3x293/code-crew
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 90 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00019 $0.00090
Opus 5 $0.00010 $0.00045
Sonnet 5 $0.00004 $0.00018
Haiku 4.5 $0.00002 $0.00009

Measured 2d ago against content hash ec74fa061ea5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

crew-rollback 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 2d 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.

commands/crew-rollback.md · 13 lines

What it actually says

Invoke the codecrew:task-rollback skill.

The rollback skill will:

  1. Read the last task from crew-history.json
  2. Show the user what files will be reverted
  3. Ask for confirmation before proceeding
  4. Use git to revert changes
  5. Update the codebase index for reverted files
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. 2d ago First seen · 13 lines · 19 tokens per session scan A ec74fa061ea5

Subscribe to this mod's changes

crew-rollback is a command published in the GitHub repository d3x293/code-crew (13 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 90 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.