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/commit)<a href="https://agentmods.dev/commands/googilyboogily/googilyboogily-claude-power-tools/commit"><img src="https://agentmods.dev/badge/commands/googilyboogily/googilyboogily-claude-power-tools/commit/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/commit"><img src="https://agentmods.dev/badge/commands/googilyboogily/googilyboogily-claude-power-tools/commit.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.00009 | $0.00989 |
| Opus 5 | $0.00005 | $0.00495 |
| Sonnet 5 | $0.00002 | $0.00198 |
| Haiku 4.5 | $0.00001 | $0.00099 |
Grade A, and why
commit 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 9d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a git commit following the project's established style
Git Expert Integration
For complex commit scenarios (merge commits, conflict resolution, commit history issues, interactive rebasing), consider using the Task tool with git-expert subagent for specialized git expertise.
Efficiency Note:
This command intelligently reuses recent git:status results when available to avoid redundant operations. If you just ran /git:status, the commit process will be faster.
When git conventions are already documented in CLAUDE.md/AGENTS.md, use them directly without verbose explanation.
All git commands are combined into a single bash call for maximum speed.
Steps:
- Check if the previous message contains git:status results:
- Look for patterns like "Git Status Analysis", "Modified Files:", "Uncommitted Changes:"
- If found and recent (within last 2-3 messages): Reuse those results
- If not found or stale: Run a single combined git command: !git --no-pager status --porcelain=v1 && echo "---STAT---" && git --no-pager diff --stat 2>/dev/null && echo "---DIFF---" && git --no-pager diff 2>/dev/null | head -2000 && echo "---LOG---" && git --no-pager log --oneline -5
- Note: Only skip git status if you're confident the working directory hasn't changed
- Note: Full diff is capped at 2000 lines to prevent context flooding. The stat summary above shows all changed files
- Review the diff output to verify:
- No sensitive information (passwords, API keys, tokens) in the changes
- No debugging code or console.log statements left in production code
- No temporary debugging scripts (test-.js, debug-.py, etc.) created by Claude Code
- No temporary files or outputs in inappropriate locations (move to project's temp directory or delete)
- All TODO/FIXME comments are addressed or intentionally left
- Use documented git commit conventions from CLAUDE.md/AGENTS.md
- If conventions are not documented, analyze recent commits and document them
- If the project uses ticket/task codes, ask the user for the relevant code if not clear from context
- Check if README.md or other documentation needs updating to reflect the changes (see "Documentation Updates" section below)
- Run tests and lint commands to ensure code quality (unless just ran before this command)
- Stage all relevant files (including any updated documentation)
- Create commit with appropriate message matching the project's conventions
- Verify commit succeeded - Report with ✅ success indicator
- Check if any post-commit hooks need to be considered (e.g., pushing to remote, creating PR)
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.
- 9d ago First seen · 76 lines · 9 tokens per session scan A 169f450b42f4
commit is a command published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 989 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
commit
A Git commit command that reviews your changes and creates a Conventional Commits message, a standard format for describing what a change does.
make-pr
Render a cognitive-aid PR body from flow-next state and open via gh.
commit
Create a git commit using the Haiku model.
orc
Parallel multi-agent orchestration for complex features.
parallel-task
Execute bulk modifications across codebase with parallel agents and safety guarantees.
pwf-commit-changes
Commit uncommitted changes across all workspace repos, tagging commits with ticket numbers from pasted issue text. Spawns one parallel subagent per repo — each analyzes every changed file, groups them by ticket, and makes multiple focused commits independently.