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/xbim08/awesome-claude-code-plugins/commit-push-prgit clone --depth 1 https://github.com/xbim08/awesome-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.00008 | $0.00200 |
| Opus 5 | $0.00004 | $0.00100 |
| Sonnet 5 | $0.00002 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
commit-push-pr 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.
This is a copy
100% identical to commit-push-pr — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Context
- Current git status: !
git status - Current git diff (staged and unstaged changes): !
git diff HEAD - Current branch: !
git branch --show-current
Your task
Based on the above changes:
- Create a new branch if on main
- Create a single commit with an appropriate message
- Push the branch to origin
- Create a pull request using
gh pr create - You have the capability to call multiple tools in a single response. You MUST do all of the above in a single message. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.
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 · 21 lines · 8 tokens per session scan A 3bc3d1719391
commit-push-pr is a command published in the GitHub repository xbim08/awesome-claude-code-plugins (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 8 tokens to every session and 200 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to commit-push-pr, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
workflow-from-spec
Design a complete multi-agent workflow from a natural language description, selecting the right orchestration pattern.
create-hook
Create hooks with brainstorming and security-first design.
evaluate-skill
Manually evaluate a recent skill execution to record qualitative feedback.
team-standup
Generate a team standup summary using the shared team log and individual context.
atl-fetch-jira
Command "atl-fetch-jira" from lc-semba-ryuichiro/semba-claude-plugins, covering jira 情報取得コマンド, コマンド実行, オプション, 実行例 and 課題情報を取得（json）.
pr-desc
Reads git diff between the current branch and main (or a specified base branch), analyzes changed files, and generates a structured pull request description ready to paste into GitHub.