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.
git clone --depth 1 https://github.com/GoogilyBoogily/googilyboogily-claude-power-toolsWrote 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/googilyboogily/googilyboogily-claude-power-tools/restore)<a href="https://agentmods.dev/commands/googilyboogily/googilyboogily-claude-power-tools/restore"><img src="https://agentmods.dev/badge/commands/googilyboogily/googilyboogily-claude-power-tools/restore/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/commands/googilyboogily/googilyboogily-claude-power-tools/restore"><img src="https://agentmods.dev/badge/commands/googilyboogily/googilyboogily-claude-power-tools/restore.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.00006 | $0.00417 |
| Opus 5.5 | $0.00002 | $0.00167 |
| Sonnet 5.5 | $0.00001 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
restore 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 1mo 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.
What it actually says
Restore to checkpoint
Restore your project files to a previous checkpoint created with /checkpoint.
Available checkpoints
!git stash list | grep "claude-checkpoint" | head -10
Current status
!git status --short
Task
Restore the project to a previous checkpoint. Based on $ARGUMENTS:
-
Parse the argument:
- If empty or "latest": Find the most recent claude-checkpoint stash
- If a number (e.g. "2"): Use stash@{2} if it's a claude-checkpoint
- Otherwise: Show error and list available checkpoints
-
Check for uncommitted changes with
git status --porcelain. If any exist:- Create a temporary backup stash:
git stash push -m "claude-restore-backup: $(date +%Y-%m-%d_%H:%M:%S)" - Note the stash reference for potential recovery
- Create a temporary backup stash:
-
Apply the checkpoint:
- Use
git stash apply stash@{n}(not pop, to preserve the checkpoint) - If there's a conflict due to uncommitted changes that were stashed, handle gracefully
- Use
-
Show what was restored:
- Display which checkpoint was applied
- If uncommitted changes were backed up, inform user how to recover them
Example outputs:
- For
/restore: "Restored to checkpoint: before major refactor (stash@{0})" - For
/restore 3: "Restored to checkpoint: working OAuth implementation (stash@{3})" - With uncommitted changes: "Backed up current changes to stash@{0}. Restored to checkpoint: before major refactor (stash@{1})"
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.
- 1mo ago First seen · 42 lines · 6 tokens per session scan A e5179498969b
restore is a command published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 417 once invoked, about $0.0000 per session on Opus 5.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
context
A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.
clean-branches
A Git command for finding and safely removing local or remote branches that are already merged or have not been updated for a chosen number of days. Git branches are separate lines of code history used for features, fixes, or experiments.
rollback
An interactive Git command for moving a branch back to an earlier commit, tag, or saved reference. It supports reset, which changes branch history, and revert, which adds new commits that undo earlier ones.
land
Resolve and squash merge one named, currently authorized pull request.
resolve-pr
Resolve PR review feedback — fetch unresolved threads, triage, dispatch resolver agents, reply + resolve via GraphQL.
wrap
The session-scoped landing step after ship: flips board rows, merges green PRs, checks deploys, tidies worktrees, prints the skim-first report. Use when the operator says to wrap up, close out the session, or land the work: 'wrap up', 'close out', 'session wrap', 'land it', 'tổng kết session', 'wrap lại đi'. Also the…