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/krmcbride/claude-plugins/amend-commitgit clone --depth 1 https://github.com/krmcbride/claude-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.00016 | $0.00935 |
| Opus 5 | $0.00008 | $0.00467 |
| Sonnet 5 | $0.00003 | $0.00187 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
amend-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 yesterday.
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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Amend the last commit with a well-crafted message following conventional commit best practices.
User Input
$ARGUMENTS
Amend Commit Workflow
Step 1: Scope
This command ONLY amends the message of the last commit. It does NOT:
- Add or stage any files
- Include uncommitted changes
- Push to remote
- Modify any commits other than HEAD
Verify there is at least one commit by running git rev-parse HEAD.
Step 2: Gather Context
Run these commands to understand the commit:
# Current commit message
git log -1 --format=%B
# Commit statistics (files changed, insertions, deletions)
git show --stat HEAD
# Full diff for analysis
git show HEAD
Also note any type override or additional context from the user input above.
Step 3: Analyze and Draft New Message
Based on the diff, craft a new commit message following this format:
Subject Line (~72 chars)
type(scope): imperative description
Determine type from diff characteristics (user override takes precedence):
feat- New functionality, new files that add capabilitiesfix- Bug fixes, error correctionsrefactor- Code restructuring without changing behaviordocs- Documentation, README, commentsstyle- Formatting, whitespace, linting (no logic change)test- Adding or updating testschore- Maintenance, dependencies, toolingperf- Performance improvementsbuild- Build system, CI configurationci- CI/CD pipeline changes
Derive scope - use a short service, module, or feature name (not a file path):
- Prefer domain concepts:
auth,billing,search,api - Use feature names when appropriate:
login,checkout,export - For libraries/packages: use the package name
- If changes span multiple areas, use the most significant or omit scope entirely
- Keep it short (ideally 3-10 chars) to leave room for the description
Write description in imperative mood:
- "add user authentication" not "added user authentication"
- "fix null pointer in parser" not "fixes null pointer"
- No period at the end
- Lowercase after the colon
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.
- yesterday First seen · 164 lines · 16 tokens per session scan A f83e08a09535
amend-commit is a command published in the GitHub repository krmcbride/claude-plugins (3 stars, last pushed 8mo ago), licensed MIT. It adds 16 tokens to every session and 935 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-31.
Other commands, from other repositories
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.