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 skills/paulrberg/agent-skills/git-squashnpx skills add PaulRBerg/agent-skills --skill git-squashgit clone --depth 1 https://github.com/PaulRBerg/agent-skillsWrote 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/paulrberg/agent-skills/git-squash)<a href="https://agentmods.dev/skills/paulrberg/agent-skills/git-squash"><img src="https://agentmods.dev/badge/skills/paulrberg/agent-skills/git-squash.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.1 | $0.00027 | $0.00892 |
| Opus 5 | $0.00014 | $0.00446 |
| Sonnet 5 | $0.00005 | $0.00178 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
git-squash 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 6d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Squash
If these instructions are already present in the conversation from a slash or dollar invocation, follow them directly; do not invoke this skill again through a skill tool.
Squash the current feature branch into one commit representing its net change relative to the resolved default branch.
Arguments
--subject <line>: require this exact first line in the replacement commit message.--base <branch>: override default-branch detection.
Without --subject, the agent writes a conventional-commit subject from the surviving net diff. Without --base, the
helper resolves origin/HEAD, then origin's advertised head, then local/remote main, master, or trunk.
Plan Interface
Resolve the helper from this SKILL.md. Write its JSON to a scratch path outside the repository so preflight remains
clean:
uv run "<skill-dir>/scripts/git-squash.py" plan \
[--cwd <repo>] [--base <branch>] [--subject <line>] > <plan.json>
plan is read-only. It verifies the Git worktree, attached branch, clean tree/index, resolved base, non-default current
branch, merge base, positive ahead count, and remote facts. It returns schemaVersion: 1, the immutable original HEAD,
merge base, base ref, commits in chronological order, unique authors, tree/remote state, and rollback facts. A failed
precondition exits without changing history.
Show the branch, base ref, merge base, commits replaced, tree state, remote state, and rollback HEAD in a compact plain table before mutation.
Agent-Owned Commit Message
Inspect the plan's commits and the net diff from mergeBase..originalHead. The net diff is authoritative; intermediate
commits supply intent and attribution only. Inspect targeted hunks when the summary is ambiguous.
Use --subject exactly when supplied. Otherwise choose the conventional type from the surviving outcome: feat, fix,
refactor, docs, test, build, ci, chore(deps), style, perf, ai, or chore. Do not call the change
chore merely because it is a squash.
What ships with it
2 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.
- 6d ago First seen · 80 lines · 27 tokens per session scan A 71c910ed1441
git-squash is a skill published in the GitHub repository PaulRBerg/agent-skills (70 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 892 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 skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. 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.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
commit
Commit current changes with a clear, descriptive message.
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…
create-hotfix
Create a hotfix (patch) release branch for an Azure SDK Rust crate.