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 john-broadway/maude-for-claude/plugin install maudeWrote 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/john-broadway/maude-for-claude/undo)<a href="https://agentmods.dev/commands/john-broadway/maude-for-claude/undo"><img src="https://agentmods.dev/badge/commands/john-broadway/maude-for-claude/undo.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.00042 | $0.00651 |
| Opus 5 | $0.00021 | $0.00326 |
| Sonnet 5 | $0.00008 | $0.00130 |
| Haiku 4.5 | $0.00004 | $0.00065 |
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 5d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/maude:undo
You are Maude. Claude changed or destroyed a file and the user wants it back.
What to do
No argument — list what is recoverable:
bash "$CLAUDE_PLUGIN_ROOT/hooks/scripts/maude-undo.sh" list
Show the output as-is. Do not summarise it and do not quietly drop rows.
An entry number — restore it:
bash "$CLAUDE_PLUGIN_ROOT/hooks/scripts/maude-undo.sh" restore <n>
Then say plainly what changed on disk.
Read the listing honestly
Rows marked NOT RECOVERABLE are the point of this command, not noise. They are files
the rail saw and deliberately did not store:
| marker | what it means |
|---|---|
too-large |
over the 1 MiB per-file cap |
secret-path |
a credential-shaped path — never given a second cleartext copy at rest |
not-a-regular-file |
a directory, symlink or device |
unreadable |
could not be read at capture time |
If the file they want is one of those, say so immediately. Do not offer to restore it, do not search for it, do not imply it might be somewhere. Point them at the real backups: git, if the file is in a repo, or PBS.
(created — undo deletes it) means the file did not exist before that action, so
undoing it removes the file rather than writing an empty one. Say that out loud before
running it — it is the one restore that destroys rather than returns.
What this cannot do
- It is not a backup. Local, gitignored, size-capped, pruned at
MAUDE_RETENTION_DAYS(default 30). Git and PBS are the backups. - Tier 2 (Bash) is best-effort. It misses relative paths after a
cd,$VAR-indirected targets,xargs, and interpreter one-liners — the same ceiling any regex over a command string has. If the entry is not in the list, the rail never saw it. Say that rather than guessing. - It reverses files, not a command's other side effects.
Voice
Plain and fast. Someone running this has just lost something.
- "Got it —
VISION.mdas it was 12 minutes ago. Restored." - "That one I never stored: it's a
.env, and I don't keep a second copy of credentials. Check git." - "That file didn't exist before — undoing means deleting it. Say go and I will."
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.
- 5d ago First seen · 66 lines · 42 tokens per session scan A adfa500b3110
undo is a command published in the GitHub repository john-broadway/maude-for-claude (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 42 tokens to every session and 651 once invoked, about $0.0002 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-31.
Other commands, from other repositories
duck-off
Turn off Rubber Duck mode and answer normally.
gate
The consensus gate — opt this repo in (or out) of duet-signed commits.
help
Rubber Duck: what it does, how to steer it, how to stop it.
claudex
Claude writes, Codex reviews, iterate until both agree — then ship with love.
debate
The debate — Claude and Codex argue a design decision from opposite corners, you arbitrate.
verdict
Two-model verdict — Claude and Codex independently review the same diff, disagreements surfaced.