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/onmyway133/claude-code-pluginsWrote 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/onmyway133/claude-code-plugins/commit)<a href="https://agentmods.dev/commands/onmyway133/claude-code-plugins/commit"><img src="https://agentmods.dev/badge/commands/onmyway133/claude-code-plugins/commit/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/onmyway133/claude-code-plugins/commit"><img src="https://agentmods.dev/badge/commands/onmyway133/claude-code-plugins/commit.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.00000 | $0.00463 |
| Opus 5.5 | $0.00000 | $0.00185 |
| Sonnet 5.5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00046 |
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 1mo 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
Commit
Create well-structured git commits with meaningful messages.
Usage
/commit [type]
Arguments:
type- Optional:feat,fix,refactor,docs,test,chore
Commit Process
Step 1: Analyze Changes
Run these commands to understand what changed:
git status
git diff --staged
git diff
If nothing is staged, ask whether to stage all changes or specific files.
Step 2: Categorize Changes
Determine the primary change type:
| Type | When to Use |
|---|---|
feat |
New feature or capability |
fix |
Bug fix or correction |
refactor |
Code restructuring (no behavior change) |
docs |
Documentation only |
test |
Adding or updating tests |
chore |
Build, tooling, dependencies |
Step 3: Craft the Message
Follow this format:
<type>: <concise summary in imperative mood>
<optional body explaining what and why>
<optional footer with references>
Rules:
- Summary line: 50 chars or less, imperative mood ("Add" not "Added")
- Body: Wrap at 72 chars, explain motivation and context
- Footer: Issue references, breaking changes
Good Examples:
feat: add user authentication with JWT tokens
Implement login/logout flow with secure token storage.
Tokens expire after 24 hours and refresh automatically.
Closes #123
fix: prevent crash when network unavailable
Handle nil response gracefully instead of force unwrapping.
Bad Examples:
fixed stuff # Too vague
WIP # Not descriptive
Updated files # Says nothing useful
Step 4: Execute
Stage files if needed and create the commit:
git add <files>
git commit -m "<message>"
Show the result with git log -1.
Guidelines
- One logical change per commit
- Don't mix unrelated changes
- Never commit secrets or credentials
- Reference issues when applicable
- Keep commits atomic and revertable
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.
- 1mo ago First seen · 99 lines · 0 tokens per session scan A c0cfe80a9333
commit is a command published in the GitHub repository onmyway133/claude-code-plugins (5 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 463 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
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
pre-pr-check
Perform a comprehensive pre-PR check: summarize changes, analyze risk, and generate a review checklist.
make-pr
Render a cognitive-aid PR body from flow-next state and open via gh.
pr
A guided command for preparing a GitHub Pull Request, which is a proposed set of repository changes for review and merging. It reads the branch history and changed files to draft the request.
commit
Based on the above changes, create a single git commit.
git-commit
Based on the above changes, create a single git commit. Use the Angular commit message format：.