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.
npx agentmods add commands/bengous/claude-code-plugins/analyze-gitgit clone --depth 1 https://github.com/bengous/claude-code-pluginsWhat 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 | $0.00000 | $0.00497 |
| Opus 5 | $0.00000 | $0.00249 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
analyze-git 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 yesterday.
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Git Repository for Cleanup
Perform a comprehensive analysis of the git repository to identify branches and worktrees that can be cleaned up. This is a READ-ONLY analysis - no deletions will be performed.
Step 1: Analyze Local Branches with [gone] Status
Run the following command to identify branches whose remote tracking branches no longer exist:
git branch -v
Look for branches marked with [gone] status. These are local branches whose remote counterparts have been deleted.
Step 2: Analyze Worktrees
Run the following command to list all worktrees:
git worktree list
Identify any worktrees marked as "prunable" - these can be safely removed.
Step 3: Analyze Dependabot Branches
- First, update remote references:
git fetch --prune
- List all dependabot PRs and their status:
gh pr list --state all --limit 100 --json number,title,state,headRefName --jq '.[] | select(.headRefName | startswith("dependabot/")) | "PR #\(.number): \(.headRefName) - \(.state)"'
- List current remote dependabot branches:
git branch -r | grep 'dependabot/'
Cross-reference to find dependabot branches with CLOSED or MERGED PRs that still have remote branches.
Step 4: Analyze Other Stale Branches
List all local and remote branches to identify any other stale branches:
git branch
git branch -r
Step 5: Provide Summary Report
Create a comprehensive summary report with:
- Gone Branches: List of local branches marked [gone] with worktree indicators
- Prunable Worktrees: List of worktrees that can be pruned
- Closed Dependabot PRs: List of dependabot branches with closed/merged PRs
- Branch Inventory: Total count of local and remote branches
Format the report clearly with counts and specific branch names.
End with: "Run /git-tools:cleanup-git to perform the cleanup operations."
Important Notes
- This command performs NO modifications
- All operations are read-only
- Use this to review what needs cleanup before running
/git-tools:cleanup-git
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.
- yesterday First seen · 71 lines · 0 tokens per session scan A 04f6aa1c684a
analyze-git is a command published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 497 tokens. 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
pr-address
Address PR review comments on current branch.
plan-save
Save the current session's plan to GitHub as an issue.
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.
OPSX: Sync
Sync delta specs from a change to main specs.
context
项目上下文管理：初始化 .context 目录、记录决策日志、压缩归档、查看历史.
OPSX: Verify
Verify implementation matches change artifacts before archiving.