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/fusengine/agents/amendgit clone --depth 1 https://github.com/fusengine/agentsWrote 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/commands/fusengine/agents/amend)<a href="https://agentmods.dev/commands/fusengine/agents/amend"><img src="https://agentmods.dev/badge/commands/fusengine/agents/amend.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.00020 | $0.00331 |
| Opus 5 | $0.00010 | $0.00166 |
| Sonnet 5 | $0.00004 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
amend 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.
What it actually says
Amend Last Commit
Current State
!git status
Last Commit
!git log -1 --pretty=format:'%h %s%n%b'
Remote Status
!git log origin/HEAD..HEAD --oneline 2>/dev/null || echo "No remote tracking"
Instructions
Safely amend the last commit.
Security Check (MANDATORY)
IF the last commit is already pushed to remote:
- REFUSE to amend
- Explain: "Cannot amend pushed commits. This would require force push."
- Suggest: Create a new
fix(scope): correct previous commitinstead
IF the last commit is NOT pushed:
- Stage new changes:
git add -A - Ask: "Keep same message or provide new one?"
- NO AI SIGNATURE: Never add Co-authored-by, Generated by, or any AI mention
- Execute:
- Same message:
git commit --amend --no-edit - New message:
git commit --amend -m "new message"
- Same message:
- Show result with
git log -1
Warning
NEVER use --force push after amend on shared branches (main, master, develop).
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 · 45 lines · 20 tokens per session scan A 2ff72ae12644
amend is a command published in the GitHub repository fusengine/agents (25 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 331 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-09-03.
Other commands, from other repositories
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).
commit
Analyze git diffs or staged changes and generate conventional commit messages that explain WHY a change was made. Supports auto-detecting type and scope, intelligent file staging, and interactive overrides. Use when asked to "write a commit message", "generate a commit", "describe my changes", "commit this"…
nyann:commit
Generate a Conventional Commits message from the staged diff and commit after confirmation. Same flow as the natural-language commit skill — dispatches here so users who prefer explicit slash commands can bypass intent detection.
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.