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 skills add motlin/claude-code-plugins --skill 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/reword-commits)<a href="https://agentmods.dev/skills/motlin/claude-code-plugins/reword-commits"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/reword-commits/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/motlin/claude-code-plugins/reword-commits"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/reword-commits.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.00045 | $0.00693 |
| Opus 5.5 | $0.00018 | $0.00277 |
| Sonnet 5.5 | $0.00009 | $0.00139 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
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 22d 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reword Commits
Use the code:cli and git:git-workflow skills. The message format in git:git-workflow is the target.
Rewrite every commit message in scope. Don't triage, and don't skip commits whose subjects already look fine: every commit gets a fresh proposal.
Constraints
Use git history reword only: no interactive rebase, git commit --amend, git filter-branch, git filter-repo, or git replay. No branch switching, no force-pushing, and no changes to content, authors, dates, parents, or trees. Messages only.
Scope
By default, reword the current branch's commits that aren't on its upstream: <upstream>..HEAD, falling back to main..HEAD or master..HEAD. If none apply, ask which base to use via AskUserQuestion.
If the user asks for "all branches", collect each local branch's commits not on its upstream (or the main/master fallback). A commit shared across branches is rewritten once, since git history reword updates every branch that contains it.
Anything else the user wrote is extra guidance on top of git:git-workflow. If the set is empty, say so and stop.
Reading Each Commit
Read the full message, subject and body, for every commit. A body is itself a violation of the single-line rule.
git log --format='%H%n%B%n--END-COMMIT--' <range>
git show --no-patch --format=%B <sha>
If a message's intent is unclear, read the diff with git show <sha>.
Drafting and Confirming
For each commit, draft one line that distills the full prior message (subject and body) and applies the user's extra guidance. Show before/after for every commit, noting any body being collapsed:
<short-sha> BEFORE: <current subject> [+ N-line body]
AFTER: <proposed single-line message>
Then ask via AskUserQuestion:
- "Apply all rewrites" (recommended)
- "Apply a subset" (ask which SHAs)
- "Regenerate proposals"
- "Cancel"
Applying
Run git history reword <sha> for each approved commit, oldest first, with a GIT_EDITOR that overwrites the whole message file so the body is dropped too:
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.
- 22d ago Changed · -23 lines 07526c69d4c1
- 1mo ago First seen · 89 lines · 45 tokens per session scan A f759063ff687
reword-commits is a skill published in the GitHub repository motlin/claude-code-plugins (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 693 once invoked, about $0.0002 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-09-19.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
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…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.