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 drn/dots --skill squashgit clone --depth 1 https://github.com/drn/dotsWrote 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/drn/dots/squash)<a href="https://agentmods.dev/skills/drn/dots/squash"><img src="https://agentmods.dev/badge/skills/drn/dots/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.00035 | $0.01037 |
| Opus 5 | $0.00017 | $0.00518 |
| Sonnet 5 | $0.00007 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00104 |
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 3d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Current branch: !
git branch --show-current - Git status: !
git status --porcelain 2>/dev/null | head -20 - Base ref: !
git branch -r 2>/dev/null | grep -oE 'origin/(main|master)' | head -1 - Commits vs main: !
git log origin/main..HEAD --oneline 2>/dev/null | head -50 - Commits vs master: !
git log origin/master..HEAD --oneline 2>/dev/null | head -50 - Open PR: !
gh pr view --json number,url,title,headRefName 2>/dev/null | head -10 - Remote tracking: !
git rev-parse --abbrev-ref @{upstream} 2>/dev/null | head -1 - Arguments: $ARGUMENTS
Your task
Squash all commits on the current branch (since it diverged from the default branch) into a single commit, then force-push to update any open PR.
In all steps below, substitute <remote> and <default-branch> with the values determined in Step 1.
Step 0: Validate state
- If HEAD is detached, stop: "Cannot squash in detached HEAD state."
- If the working tree has uncommitted changes (
git status --porcelain), stop: "Working tree is dirty. Commit or stash changes first." - Determine the current branch. If it is the default branch (main/master), stop: "Cannot squash commits on the default branch."
Step 1: Determine the base branch and fetch
- If
upstreamremote exists, use it. Otherwise useorigin. - Detect the default branch: try
git symbolic-ref refs/remotes/<remote>/HEAD, then<remote>/main, then<remote>/master. - If none work, stop: "Could not determine the default branch."
- Fetch the latest:
git fetch <remote> <default-branch> - Compute and store the merge base SHA:
git merge-base <remote>/<default-branch> HEAD. Use this SHA in all subsequent steps.
Step 2: Count commits
- Run
git log <merge-base-SHA>..HEAD --onelineto list branch commits. - If there are 0 commits, stop: "No commits to squash."
- If there is exactly 1 commit, stop: "Only one commit on this branch. Nothing to squash."
- Report: "Found N commits to squash."
Step 3: Draft the squash commit message
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.
- 3d ago First seen · 96 lines · 35 tokens per session scan A 54b143168c39
squash is a skill published in the GitHub repository drn/dots (23 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 1,037 once invoked, about $0.0002 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 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.
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…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…