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/gzupark/claude-plugin-pack/commitgit clone --depth 1 https://github.com/GzuPark/claude-plugin-packWhat 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.00004 | $0.00363 |
| Opus 5 | $0.00002 | $0.00181 |
| Sonnet 5 | $0.00001 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00036 |
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 2d 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
Git Commit
Create a well-structured git commit based on the current changes.
Additional Context from User
$ARGUMENTS
Context
Gather information about the current repository state:
- Current git status: !
git status - Current git diff (staged and unstaged changes): !
git diff HEAD 2>/dev/null || git diff - Current branch: !
git branch --show-current - Recent commits: !
git log --oneline -10 2>/dev/null || echo "No commits yet"
Your Task
Based on the above changes, create a single git commit.
Commit Message Guidelines
- Subject line: Use imperative mood, max 50 characters (e.g., "Add user authentication", "Fix memory leak in parser")
- Body (if needed): Explain the "why" rather than the "what", wrap at 72 characters
- Format: Follow conventional commit style when appropriate (feat, fix, docs, refactor, test, chore)
Execution
- Stage relevant files and create the commit using a single message.
- Use unordered lists (bullet points) in the commit body when describing multiple changes or points.
- Do NOT include "Generated with Claude Code", "Co-Authored-By", or any AI attribution in the commit message unless the user explicitly requests it.
- Do not use any other tools or do anything else.
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.
- 2d ago First seen · 46 lines · 4 tokens per session scan A 5f1f44d24e4f
commit is a command published in the GitHub repository GzuPark/claude-plugin-pack (6 stars, last pushed 7mo ago), licensed MIT. It adds 4 tokens to every session and 363 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.