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/motlin/claude-code-plugins/reword-commitsgit clone --depth 1 https://github.com/motlin/claude-code-pluginsWhat 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.00021 | $0.00899 |
| Opus 5 | $0.00010 | $0.00449 |
| Sonnet 5 | $0.00004 | $0.00180 |
| Haiku 4.5 | $0.00002 | $0.00090 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rewrite every commit message in scope to a single line that follows the git-workflow skill. Do not triage. Do not skip commits whose subjects already look fine — if the user invoked this command, every commit needs a fresh message.
ALWAYS use the code:cli and git-workflow skills. The rules in git-workflow are what to write toward.
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, no changes to commit content, authors, dates, parents, or trees. Messages only.
Scope
The user passed in: $ARGUMENTS
Default scope is commits on the current branch that aren't on its upstream (or on main/master if there is no upstream). If the arguments ask for a wider scope like "all branches", expand to cover every local branch's unique commits. Anything else in the arguments is extra guidance to apply on top of the git-workflow rules.
Picking the commit set
For the default scope, use <upstream>..HEAD if the branch has an upstream, otherwise main..HEAD or master..HEAD. If none of those apply, ask which base to use via AskUserQuestion.
For "all branches", collect commits reachable from each local branch but not from its upstream (or main/master fallback). A commit shared across branches gets rewritten once — git history reword updates every branch that contains it.
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, so you have to see it to fix it.
Stream every full message in scope with this command:
git log --format='%H%n%B%n--END-COMMIT--' <range>
For one commit at a time:
git show --no-patch --format=%B <sha>
If a message's intent isn't clear from the text, run git show <sha> to see the diff.
Drafting
For every commit in scope, draft a replacement single-line message that:
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 · 89 lines · 21 tokens per session scan A 93e51d5ce29e
reword-commits is a command published in the GitHub repository motlin/claude-code-plugins (15 stars, last pushed 3d ago), licensed Apache-2.0. It adds 21 tokens to every session and 899 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.