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 MithunWijayasiri/dotclaude --skill empty-commitgit clone --depth 1 https://github.com/MithunWijayasiri/dotclaudeWrote 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/mithunwijayasiri/dotclaude/empty-commit)<a href="https://agentmods.dev/skills/mithunwijayasiri/dotclaude/empty-commit"><img src="https://agentmods.dev/badge/skills/mithunwijayasiri/dotclaude/empty-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/mithunwijayasiri/dotclaude/empty-commit"><img src="https://agentmods.dev/badge/skills/mithunwijayasiri/dotclaude/empty-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.00035 | $0.00547 |
| Opus 5.5 | $0.00014 | $0.00219 |
| Sonnet 5.5 | $0.00007 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
empty-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 9d 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.
What it actually says
Empty Commit
Empty commit + push → CI re-runs on the current branch. Zero file changes, so nothing can regress.
Any step fails → stop, report what failed; do not work around.
-
Nothing staged:
git diff --cached --quiet. Non-zero →--allow-emptywould commit the staged files; list them (git diff --cached --name-only), stop. -
Branch:
git rev-parse --abbrev-ref HEAD.HEAD(detached),main, ormaster→ stop; empty commit on a shared branch is noise. -
Upstream:
git rev-parse --abbrev-ref --symbolic-full-name @{u}. Fails → no upstream set; stop, ask user which case: never pushed →git push -u origin <branch>alone triggers CI; already pushed without-u→git branch -u <remote>/<branch>, re-run (re-pushing the same commit triggers nothing). -
Commit, subject only, no trailer of any kind:
git commit --allow-empty -m "chore: trigger pipeline re-run" -
git push. Fails → commit exists locally, not pushed; say so. -
Report one line: short SHA, branch, PR link if push output printed one.
Unstaged and untracked files are ignored, they stay untouched.
Caveat — which pipelines this actually re-runs
Only pipelines triggered by a push to the branch or its PR. Config varies by provider:
| Provider | Re-runs | Does not re-run |
|---|---|---|
| GitHub Actions | on: push, on: pull_request |
on: workflow_dispatch only |
| GitLab CI | jobs matching rules: / workflow:rules for the branch or MR |
when: manual jobs |
| Bitbucket Pipelines | pull-requests, branches |
custom |
Manually-triggered pipelines never fire from a commit. If the red check is one of those, an empty commit does nothing — say so and point the user at re-running it by hand, with any variables it prompts for.
Unsure which kind → check the CI config in the repo (.github/workflows/, .gitlab-ci.yml, bitbucket-pipelines.yml).
What ships with it
1 file 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.
- 9d ago Changed · +4 lines f472dd6d3279
- 11d ago First seen · 36 lines · 35 tokens per session scan A 578746606ffe
empty-commit is a skill published in the GitHub repository MithunWijayasiri/dotclaude (4 stars, last pushed 6d ago), licensed MIT. It adds 35 tokens to every session and 547 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-10-09.
Other skills, from other repositories
pr-squash-message
Generate one short Conventional Commits squash message describing only the net diff between the PR's base and head, set its header as the PR title, validate it with the repository's commitlint and both copy its description to the clipboard and display it, when asked for a squash message. Works in any Scenario…
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
ship
Commit, push, and optionally create or update a PR for the current staged changes. Use when the user asks to "ship", "ship it", "ship changes", "commit push and PR", or "ship this".
private-secret-scanning
Local Gitleaks scans for staged changes, push ranges, and full history in private repos, with redacted reports. Use to block committed secrets without GitHub Secret Protection.