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/commit-plugingit 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.00011 | $0.00932 |
| Opus 5 | $0.00005 | $0.00466 |
| Sonnet 5 | $0.00002 | $0.00186 |
| Haiku 4.5 | $0.00001 | $0.00093 |
Grade A, and why
commit-plugin 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Plugin
Commit changes to a plugin with proper semantic versioning.
Workflow
1. Identify the Plugin
If $ARGUMENTS is provided, use that as the plugin name. Otherwise, detect from staged/unstaged changes:
git status --porcelain | grep -E '^\s*[MADR?]+\s+[^/]+/' | sed 's|.*\s\+\([^/]*\)/.*|\1|' | sort -u
If multiple plugins have changes, ask the user which one to commit.
Validate the plugin exists:
test -f "<plugin-name>/.claude-plugin/plugin.json"
2. Analyze Changes
Get the diff for this plugin:
git diff HEAD -- <plugin-name>/
git diff --cached -- <plugin-name>/
git status --porcelain -- <plugin-name>/
Categorize the changes:
| Change Type | Version Impact | Examples |
|---|---|---|
| Breaking | MAJOR | Removed commands, renamed commands, changed command behavior incompatibly |
| New features | MINOR | New commands, new skills, new agents, new significant functionality |
| Fixes/improvements | PATCH | Bug fixes, documentation, refactoring, small tweaks |
3. Get Current Version
jq -r '.version' <plugin-name>/.claude-plugin/plugin.json
4. Recommend Version Bump
Based on the analysis, recommend a version bump using AskUserQuestion:
Recommend MAJOR when:
- Commands were removed or renamed
- Breaking changes to command arguments/behavior
- Major architectural rewrites
Recommend MINOR when:
- New commands added
- New skills or agents added
- Significant new functionality
Recommend PATCH when:
- Bug fixes
- Documentation updates
- Small improvements or refactoring
- No new user-facing features
Present the options with your recommendation first (marked as recommended) and explain why.
5. Bump Version
Calculate the new version based on user selection:
- MAJOR:
X.0.0(reset minor and patch) - MINOR:
x.Y.0(reset patch) - PATCH:
x.y.Z
Update the version in plugin.json:
jq --arg v "<new-version>" '.version = $v' <plugin-name>/.claude-plugin/plugin.json > tmp.json && mv tmp.json <plugin-name>/.claude-plugin/plugin.json
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 · 142 lines · 11 tokens per session scan A 693ef520205f
commit-plugin is a command published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 932 once invoked, about $0.0001 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-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.