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 LandonSchropp/agent-toolkit --skill git-edit-commitgit clone --depth 1 https://github.com/LandonSchropp/agent-toolkitWrote 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/landonschropp/agent-toolkit/git-edit-commit)<a href="https://agentmods.dev/skills/landonschropp/agent-toolkit/git-edit-commit"><img src="https://agentmods.dev/badge/skills/landonschropp/agent-toolkit/git-edit-commit/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/landonschropp/agent-toolkit/git-edit-commit"><img src="https://agentmods.dev/badge/skills/landonschropp/agent-toolkit/git-edit-commit.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.00051 | $0.00635 |
| Opus 5.5 | $0.00020 | $0.00254 |
| Sonnet 5.5 | $0.00010 | $0.00127 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
git-edit-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 1mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Edit Commit
This skill outlines how agents can edit previous commits. Agents can't use git rebase -i directly, which requires a TTY. This skill provides helper scripts instead.
REQUIRED: Always reference commits by SHA, not by HEAD-relative notation like HEAD~3.
Inspect Commits First
Run git log --oneline to get SHAs. Output is newest-first; the rebase plan is oldest-first.
Amending the Latest Commit
To fold staged changes into the most recent commit without changing its message:
git add <files>
git commit --amend --no-edit
Fixup and Squash (Recommended Shortcut)
git commit --fixup=<target-sha> # merge into target, discard message
git commit --squash=<target-sha> # merge into target, combine messages
# <oldest-sha-in-scope>^ is the parent of the oldest commit in scope; use --root if it's the first commit
scripts/non-interactive-git-rebase.sh --autosquash <oldest-sha-in-scope>^
Drop, Reorder, Edit
Use scripts/non-interactive-git-rebase.sh. Supply the plan via stdin. Use --root when the oldest commit in scope is the repository's first commit.
scripts/non-interactive-git-rebase.sh <oldest-sha-in-scope>^ <<'PLAN'
pick abc1234 Keep this commit
squash def5678 Merge this into the previous
drop ghi9012 Remove this commit entirely
PLAN
Edit
Mark the commit edit in the plan. Git pauses there. Then:
git add <files>
git commit --amend --no-edit
git rebase --continue
Reword
scripts/reword-commit.sh --sha <sha> --message "New commit message"
Rationalizations
| Thought | Reality |
|---|---|
| "I can't do interactive rebase without a TTY" | Use scripts/non-interactive-git-rebase.sh instead |
| "I'll use HEAD~N as the upstream" | Use a SHA — HEAD~N is fragile and ambiguous |
| "I'll just --amend instead" (for an older commit) | --amend only works on the latest commit; use rebase for others |
| "I'll undo the commits and redo them one by one" | Rebase rewrites history in one step — no need to redo commits |
| "I'll create a new commit to fix it" | That pollutes history; rebase is the right tool |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +1 lines · +5 tokens per session b3cf4c5e5634
- 1mo ago First seen · 71 lines · 46 tokens per session scan A 91a3f466a86d
git-edit-commit is a skill published in the GitHub repository LandonSchropp/agent-toolkit (3 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 635 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-08-31.
Other skills, from other repositories
loom-git-workflow
Git operations guidance including branching strategies, commit conventions, merge workflows, conflict resolution, and worktree management.
create-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
commit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
conventional-commit
Generer conventional commit-meldinger med Nav-relevante scopes og breaking change-format.
codex-review
Professional code review with auto CHANGELOG generation, integrated with Codex AI.
configure-git-repository
Configure a Git repository with proper .gitignore, branch strategy, commit conventions, hooks, and remote setup. Covers initial setup and common patterns for R, Node.js, and Python projects. Use when initializing version control for a new project, adding a .gitignore for a specific language or framework, setting up…