Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add anilcancakir/claude-code-plugins/plugin install pre-commit-flowWrote 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/skills/anilcancakir/claude-code-plugins/commit-changes)<a href="https://agentmods.dev/skills/anilcancakir/claude-code-plugins/commit-changes"><img src="https://agentmods.dev/badge/skills/anilcancakir/claude-code-plugins/commit-changes/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/skills/anilcancakir/claude-code-plugins/commit-changes"><img src="https://agentmods.dev/badge/skills/anilcancakir/claude-code-plugins/commit-changes.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.00024 | $0.00441 |
| Opus 5.5 | $0.00010 | $0.00176 |
| Sonnet 5.5 | $0.00005 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
commit-changes 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 Task
Create a commit for staged/unstaged changes following project conventions.
Steps
- Check
git statusfor changes - Analyze
git log --oneline -10to detect commit style - Categorize changes (feat/fix/docs/refactor/test/chore)
- Generate commit message matching detected style
- Present to user for approval
- Execute commit
Commit Style Detection
Use the detection script for accurate results:
# Returns JSON with style and confidence
"${CLAUDE_PLUGIN_ROOT}/scripts/detect-commit-style.sh"
Output example:
{
"style": "conventional-scoped",
"confidence": 80,
"stats": { "total": 10, "conventional_scoped": 8, "gitmoji": 2 }
}
| Pattern | Style |
|---|---|
type(scope): message |
Conventional Commits (scoped) |
type: message |
Conventional (no scope) |
:emoji: message |
Gitmoji |
| Plain text | Simple |
Conventional Commits Types
| Type | Use For |
|---|---|
| feat | New features |
| fix | Bug fixes |
| docs | Documentation only |
| style | Formatting changes |
| refactor | Code restructuring |
| perf | Performance improvements |
| test | Adding/fixing tests |
| chore | Maintenance tasks |
Message Format
<type>(<scope>): <subject>
<body>
<footer>
Subject Rules:
- Imperative mood ("add" not "added")
- No period at end
- Max 50 characters
- Lowercase
Body (optional):
- Explain what and why
- Wrap at 72 characters
Footer (optional):
Closes #123BREAKING CHANGE: description
Output
Present message for approval before committing.
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 · 84 lines · 24 tokens per session scan A 6b19f6f33bb3
commit-changes is a skill published in the GitHub repository anilcancakir/claude-code-plugins (6 stars, last pushed 8mo ago), licensed MIT. It adds 24 tokens to every session and 441 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
review
Structured code review with parallel audit agents, confidence-scored triage, and optional auto-fix. Examines uncommitted changes, staged diffs, commit ranges, or specific paths. Produces a tiered report (MUST-FIX / RECOMMENDED / NIT) backed by evidence, then optionally applies fixes with verification.
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
smart-commit
Create clean Conventional Commits: inspect the diff, group related changes, run quality checks, and write type(scope) messages. Use when committing work, or when the user runs /smart-commit or asks to commit changes.
git-flow
Use when creating a branch, using worktrees for parallel work, committing, or wrapping up. Covers branch naming, conventional commits, short-lived branches, worktree isolation, and final merge/cleanup.
developer-git-workflow
GIT WORKFLOW — extracted from roles.json deepPrompt for developer.
wrap-up-branch
Finish a feature branch: add missing tests, review and fix the code, align docs, then merge only after explicit confirmation.