undo

An undo command for Countbean, a bookkeeping application whose changes are stored as commits in a history. It can show recent changes or create a new commit that reverses one.

In plain words
What is it for?
Use it to review recent book history, revert a chosen commit, and confirm the resulting book status.
Why use it?
It lets you back out an unwanted bookkeeping change while keeping a record of the reversal.

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/cputester5465/countbean-plugin/undo
Clone the repo
git clone --depth 1 https://github.com/CPUtester5465/countbean-plugin
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 133 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.00015 $0.00133
Opus 5 $0.00008 $0.00067
Sonnet 5 $0.00003 $0.00027
Haiku 4.5 $0.00002 $0.00013

Measured 2d ago against content hash 70dfc85a011f, 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 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.

plugin/commands/undo.md · 15 lines

What it actually says

Help the user undo a change. Arguments: $ARGUMENTS (optional commit id).

  1. Call history to show recent commits.
  2. If $1 is a commit id, call revert(commit="$1"). Otherwise show the history and ask which change to undo.
  3. Confirm the new state with book_status.

Because every change is a git commit, reverting is always safe and itself recorded — nothing is lost, it's just a new commit that backs out the old one.

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 · 15 lines · 15 tokens per session scan A 70dfc85a011f

Subscribe to this mod's changes

undo is a command published in the GitHub repository CPUtester5465/countbean-plugin (17 stars, last pushed 7d ago), licensed MIT. It adds 15 tokens to every session and 133 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.