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/ignore-init)<a href="https://agentmods.dev/commands/googilyboogily/googilyboogily-claude-power-tools/ignore-init"><img src="https://agentmods.dev/badge/commands/googilyboogily/googilyboogily-claude-power-tools/ignore-init/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/ignore-init"><img src="https://agentmods.dev/badge/commands/googilyboogily/googilyboogily-claude-power-tools/ignore-init.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.00422 |
| Opus 5 | $0.00005 | $0.00211 |
| Sonnet 5 | $0.00002 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
ignore-init 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.
What it actually says
Initialize .gitignore for Claude Code
Set up or update the project's .gitignore file with Claude Code specific patterns.
Core Claude Code Files to Ignore
Ensure these Claude Code local configuration files are ignored:
CLAUDE.local.md- Local AI assistant instructions (root).claude/settings.local.json- Personal Claude Code settings.mcp.local.json- Local MCP server configuration (root)
Development Patterns
These common development artifacts will also be added:
temp/- Temporary working directorytemp-*/- Temporary directories with prefixtest-*/- Test directories with prefixdebug-*.js- Debug scriptstest-*.js- Test scripts*-test.js- Test files with suffix*-debug.js- Debug files with suffix
Current .gitignore Status
![ -f .gitignore ] && echo "EXISTS: .gitignore found" && echo "---CONTENTS---" && cat .gitignore || echo "MISSING: No .gitignore file found"
Task
Based on the above status:
- Create
.gitignoreif it doesn't exist - Add all patterns that aren't already present
- Preserve existing entries and comments
- Report what was added
Patterns to Add
# Claude Code local files
CLAUDE.local.md
.claude/settings.local.json
.mcp.local.json
# Temporary and debug files
temp/
temp-*/
test-*/
debug-*.js
test-*.js
*-test.js
*-debug.js
Implement this by:
- Using the gitignore status above to determine what's missing
- Adding missing patterns with appropriate comments
- Preserving the existing file structure and entries
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 · 62 lines · 9 tokens per session scan A af722fc5a3a3
ignore-init 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 422 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
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
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
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 the operator's own green PRs one at a time, checks deploys, tidies branches and worktrees, writes the activity line, calls /kit:retro when a shipped PR merged, and prints the skim-first report. Use when the operator says to wrap up or close out the…