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/checkout)<a href="https://agentmods.dev/commands/googilyboogily/googilyboogily-claude-power-tools/checkout"><img src="https://agentmods.dev/badge/commands/googilyboogily/googilyboogily-claude-power-tools/checkout/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/checkout"><img src="https://agentmods.dev/badge/commands/googilyboogily/googilyboogily-claude-power-tools/checkout.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.00008 | $0.00753 |
| Opus 5.5 | $0.00003 | $0.00301 |
| Sonnet 5.5 | $0.00002 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
checkout 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Checkout: Smart Branch Management
Create or switch to branches with intelligent naming conventions and setup.
Current Branch Status
!git branch --show-current 2>/dev/null || echo "(no branch)"
Available Branches
!git branch -a 2>/dev/null | head -20
Branch Creation Task
Based on the arguments provided: $ARGUMENTS
Parse the branch specification and create/switch to the appropriate branch.
Supported Branch Types
feature/- New features and enhancementsbugfix/- Bug fixes (non-critical)hotfix/- Urgent production fixesrelease/- Release preparation brancheschore/- Maintenance and cleanup tasksexperiment/- Experimental featuresdocs/- Documentation updatestest/- Test-related changesrefactor/- Code refactoring
Branch Naming Rules
- If argument contains
/, use as-is (e.g.,feature/user-auth) - If argument is single word, suggest adding a prefix
- Convert spaces to hyphens
- Lowercase all characters
- Remove special characters except hyphens and slashes
- Validate branch name is git-compatible
Workflow
-
Parse the branch argument:
- If empty, show current branch and available branches
- If contains
/, treat as type/name format - If single word without
/, ask for branch type or suggestfeature/
-
Validate branch name:
- Check if branch already exists locally
- Check if branch exists on remote
- Ensure name follows git conventions
- Warn if name is too long (>50 chars)
-
Create or switch branch:
- If branch exists locally:
git checkout <branch> - If branch exists only on remote:
git checkout -b <branch> origin/<branch> - If new branch:
git checkout -b <branch>
- If branch exists locally:
-
Set up branch configuration:
- For hotfix branches: Base off main/master
- For feature branches: Base off current branch or develop
- For release branches: Base off develop or main
-
Report status:
- Confirm branch switch/creation
- Show upstream tracking status
- Suggest next steps (e.g., "Ready to start working. Use /git:push to set upstream when ready to push.")
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 · 108 lines · 8 tokens per session scan A 2b736e8ba3df
checkout is a command published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 753 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-09-03.
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…