undo

A command for reversing the most recent change made by the coding agent, including Git commits or file edits. It checks the recent Git history before choosing how to undo it.

In plain words
What is it for?
Use it to remove the last commit, unstage its changes, keep changes in the working folder, or undo several recent commits.
Why use it?
It helps recover from an unwanted agent change while showing whether the change can be safely identified. Some undo options keep the work, while one permanently discards it.

Command for Claude Code

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/llcoolblaze/claude-boris/undo
Clone the repo
git clone --depth 1 https://github.com/llcoolblaze/claude-boris

Made for: Claude Code.

Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 665 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.00022 $0.00665
Opus 5 $0.00011 $0.00332
Sonnet 5 $0.00004 $0.00133
Haiku 4.5 $0.00002 $0.00067

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

Security

Grade A, and why

undo 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 3d 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.

.claude/commands/undo.md · 115 lines

How it starts

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

Undo Last Change

Current State

!git log -3 --oneline 2>/dev/null || echo "Not a git repo" !git status --short 2>/dev/null

Last Commit Details

!git log -1 --format="Author: %an%nMessage: %s%nDate: %ar" 2>/dev/null


Undo Protocol

1. Identify What to Undo

Check if last commit was made by Claude Boris:

LAST_AUTHOR=$(git log -1 --format="%an")
LAST_MSG=$(git log -1 --format="%s")

# Check for Claude markers
if echo "$LAST_MSG" | grep -qiE "claude|🤖|Generated by"; then
  echo "✅ Last commit was by Claude Boris - safe to undo"
else
  echo "⚠️ Last commit was NOT by Claude Boris"
  echo "Manual confirmation required"
fi

2. Undo Options

Option A: Undo Last Commit (keep changes staged)

git reset --soft HEAD^

Result: Commit removed, changes remain staged

Option B: Undo Last Commit (unstage changes)

git reset HEAD^

Result: Commit removed, changes remain in working directory

Option C: Undo Last Commit (discard changes)

git reset --hard HEAD^

⚠️ DESTRUCTIVE: Changes are lost

Option D: Undo Multiple Commits

git reset --soft HEAD~N  # Where N is number of commits

3. Execute Undo

Based on the analysis:

If last commit was by Claude Boris:

  • Default to --soft reset (safest)
  • Keep changes for review
  • Report what was undone

If last commit was NOT by Claude:

  • Warn user
  • Require explicit confirmation
  • Suggest alternative approaches

4. Report

↩️ Undo Complete

Reverted: [commit message]
SHA: [commit SHA]
Files affected: [count]

Changes are now: [staged/unstaged/discarded]

To restore: git reflog
To continue: make desired changes and commit

5. Safety Checks

Before undoing:

  • Verify commit is by Claude
  • Check for pushed commits (warn if pushed)
  • Offer to create backup stash
  • Log undo operation in audit log

Undo History

Track undos for reference:

echo "$(date +%Y-%m-%d_%H:%M:%S) UNDO $(git log -1 --format='%h %s')" >> .claude/undo.log

Read the full file on GitHub · 115 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. 3d ago First seen · 115 lines · 22 tokens per session scan A 682bc6713234

Subscribe to this mod's changes

undo is a command published in the GitHub repository llcoolblaze/claude-boris (48 stars, last pushed 7mo ago), licensed MIT. It adds 22 tokens to every session and 665 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.