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 fprochazka/claude-code-plugins --skill commit-allgit clone --depth 1 https://github.com/fprochazka/claude-code-pluginsWrote 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/fprochazka/claude-code-plugins/commit-all)<a href="https://agentmods.dev/skills/fprochazka/claude-code-plugins/commit-all"><img src="https://agentmods.dev/badge/skills/fprochazka/claude-code-plugins/commit-all/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/fprochazka/claude-code-plugins/commit-all"><img src="https://agentmods.dev/badge/skills/fprochazka/claude-code-plugins/commit-all.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.00014 | $0.00636 |
| Opus 5.5 | $0.00006 | $0.00254 |
| Sonnet 5.5 | $0.00003 | $0.00127 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
commit-all 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 — 57 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`
Recent commits
!`git log -n 10 --oneline --abbrev-commit`
Changed files (staged and unstaged)
!`git diff HEAD --numstat`
Commits on this branch since it diverged from the base branch (fixup candidates)
Pushed or not, these stay rewritable until the branch merges.
!`base=$(git symbolic-ref -q --short refs/remotes/origin/HEAD 2>/dev/null); base=${base:-$(git rev-parse -q --verify master >/dev/null 2>&1 && echo master || echo main)}; git log --oneline "$base..HEAD" 2>/dev/null; [ -n "$(git log --oneline "$base..HEAD" 2>/dev/null)" ] || echo "(none — HEAD is at or behind $base)"`
Files touched by those commits
!`base=$(git symbolic-ref -q --short refs/remotes/origin/HEAD 2>/dev/null); base=${base:-$(git rev-parse -q --verify master >/dev/null 2>&1 && echo master || echo main)}; git diff --name-only "$base...HEAD" 2>/dev/null | sort -u`
Your task
Load the git-workflow skill and commit all pending changes (both staged and unstaged) according to its rules. Read file diffs as needed via git diff HEAD -- <path> before staging.
Work in this order:
- Check for fixups first. For each pending change ask: would one of the branch commits above have looked different if you had known this at the time? If yes it belongs inside that commit —
git commit --fixup <sha>, not a new commit. Repairing, simplifying or rearranging code this branch introduced is a fixup. Adding new work on top of a commit that was correct as written is not, even when it touches the same files. - Apply the sibling/ancestor test to whatever remains. Ancestors — pieces that only exist because the next one needs them — are one commit, cut vertically through every layer. Siblings — independent, revertible in any order, each meaningful to someone reading
masterwho never saw this branch — stay separate. - Order by dependency: quarantined noise and standalone prerequisites first, payload next, unlocked cleanups and docs last.
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 First seen · 57 lines · 14 tokens per session scan A 11716d434da4
commit-all is a skill published in the GitHub repository fprochazka/claude-code-plugins (15 stars, last pushed 7d ago), licensed MIT. It adds 14 tokens to every session and 636 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-09-12.
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 8. 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.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
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…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.