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 skills/motlin/claude-code-plugins/git-reword-commitsnpx skills add motlin/claude-code-plugins --skill git-reword-commitsgit clone --depth 1 https://github.com/motlin/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/skills/motlin/claude-code-plugins/git-reword-commits)<a href="https://agentmods.dev/skills/motlin/claude-code-plugins/git-reword-commits"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/git-reword-commits.svg" alt="Measured on agentmods" 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 | $0.00026 | $0.00263 |
| Opus 5 | $0.00013 | $0.00131 |
| Sonnet 5 | $0.00005 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
git-reword-commits 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 3d 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 Reword Commits
Use the code:cli and git-workflow skills.
Use git history reword only. Do not use interactive rebase, amend, filter-branch, filter-repo, or replay. Do not change commit content, authors, dates, parents, or trees.
Default scope is commits on the current branch not on upstream, or not on main/master when no upstream exists. If the user asks for all branches, collect every local branch's unique commits not on its upstream or fallback base.
Read full messages:
git log --format='%H%n%B%n--END-COMMIT--' <range>
Draft a replacement one-line message for every commit. Show before/after for every commit and ask for confirmation.
Apply approved rewrites oldest first:
MSG="<new single-line message>" GIT_EDITOR='sh -c "printf %s\\n \"$MSG\" > \"$1\"" --' git history reword <sha>
If any rewrite fails, stop and report the SHA and error. Do not push.
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.
- 3d ago First seen · 29 lines · 26 tokens per session scan A e6fdf766aa66
git-reword-commits is a skill published in the GitHub repository motlin/claude-code-plugins (15 stars, last pushed 4d ago), licensed Apache-2.0. It adds 26 tokens to every session and 263 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-30.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
commit
Commit current changes with a clear, descriptive message.
commit
Create structured git commits by analyzing staged and unstaged changes and grouping them logically into one or more commits with clear, descriptive messages. Use when the user asks to commit, says "commit this" or "commit my changes", wants help writing a commit message, or has finished a chunk of work that needs…