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.
git clone --depth 1 https://github.com/dsswift/ionWrote 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/dsswift/ion/squash)<a href="https://agentmods.dev/commands/dsswift/ion/squash"><img src="https://agentmods.dev/badge/commands/dsswift/ion/squash/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/commands/dsswift/ion/squash"><img src="https://agentmods.dev/badge/commands/dsswift/ion/squash.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.00017 | $0.04837 |
| Opus 5.5 | $0.00007 | $0.01935 |
| Sonnet 5.5 | $0.00003 | $0.00967 |
| Haiku 4.5 | $0.00002 | $0.00484 |
Grade A, and why
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 17d 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 — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/squash
Rebuild current feature branch into clean conventional commits without changing tracked content. This command is history-only and fully autonomous.
No human interaction
Never call AskUserQuestion. Never pause for approval, confirmation, or
disambiguation at any point. Emit the plan, then execute it in the same turn
without waiting. Every decision has a deterministic rule below; when a rule
fires, apply it, log it as a plan revision, and continue.
The only stop conditions are the Phase A guards (§2), a pre-reset target mismatch (§6), and verified content loss (§8b). Once the rebuild starts it always runs to completion (§7b) — a plan that proves unimplementable is revised, never abandoned. Any stop is automatic and reported; it never asks.
Absolute invariants
Two, both mandatory. Neither is ever traded for the other.
I1 — Content. Final
HEAD^{tree}must equal startingHEAD^{tree}byte-for-byte.I2 — Scope. Every result commit must resolve to exactly one scope under
.commit.json, and itstype(scope):tag must be that scope.
I2 is not cosmetic. The release tool (release-damnit, configured by
release-please-config.json) versions each component by the paths a commit
touches, and takes the commit's type and subject as that component's changelog
entry. So a commit spanning two release
units bumps both and files the same subject under both changelogs — one of
them a lie. A commit whose tag disagrees with its paths ships a correct version
under a misleading entry. Both are defects equal in severity to losing content.
.commit.json keeps the tag and the paths in agreement, which is why scope is
always resolved from paths and never taken from the plan's subject line. There
is no "report the mismatch and move on" path: a scope violation is prevented
before commit (§7c) and repaired after commit (§8a).
Commit count, subjects, and grouping are all negotiable to satisfy I1 and I2. Splitting a feature into more commits, or merging features into fewer, is always permitted and preferred over shipping a wrong scope.
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.
- 17d ago Changed · +3 lines ae9abce6b75a
- 1mo ago Changed · +33 lines 9e9318db8ece
- 1mo ago Changed · +1 lines f108c9348d40
- 1mo ago First seen · 455 lines · 17 tokens per session scan A 3b2bd65cbcb7
squash is a command published in the GitHub repository dsswift/ion (4 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 4,837 once invoked, about $0.0001 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 commands, from other repositories
undo-commit
Soft-undo the last commit. Restores its changes as staged, leaves working tree intact. Refuses if HEAD is already pushed to a tracked remote.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
refactor-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
autocommit
Toggle auto git commits on/off for this project. Run without args to see status, or with "on"/"off" to set.
repo-guard.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.