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 juxt/claude-plugins --skill commitgit clone --depth 1 https://github.com/juxt/claude-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/juxt/claude-plugins/commit)<a href="https://agentmods.dev/skills/juxt/claude-plugins/commit"><img src="https://agentmods.dev/badge/skills/juxt/claude-plugins/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/juxt/claude-plugins/commit"><img src="https://agentmods.dev/badge/skills/juxt/claude-plugins/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00098 | $0.02123 |
| Opus 5.5 | $0.00039 | $0.00849 |
| Sonnet 5.5 | $0.00020 | $0.00425 |
| Haiku 4.5 | $0.00010 | $0.00212 |
Grade A, and why
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 4d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contextual Git Commit
Interpret MUST, MUST NOT, SHOULD, SHOULD NOT, MAY, etc. per RFC 2119.
The user MAY provide the commit headline as an argument (e.g. /chalk:commit fix: boolean logic error in expression.clj).
Before you draft
A commit body is an explanation artefact and MUST be drafted in the chalk voice, not your own default prose habits.
You MUST load these skills first:
-
chalk:voice— the audience, the specification register, the mindmap structure, the line-format rule. -
chalk:code-comments— the body is where a comment's design rationale belongs, so this is the moment the misfiled ones surface.
Your responsibilities
-
Stage relevant changes.
Each commit MUST be an atomic, cohesive unit of change — a transition from one valid state to another — and unrelated changes MUST NOT be staged together.
-
If two changes don't make sense independently, they're one commit; if they're distinct, they're two.
-
Keep unrelated bugfixes separate.
-
Where reasonable, separate behaviour-preserving changes (refactorings) from behaviour-advancing ones.
-
-
Weed the staged comments.
Delegate to the
weed-commentsagent, passing the paths of the staged files and nothing else.-
You MUST NOT tell it what the change is for. Not the issue, not the problem, not what you decided. It stands in for a reader who has none of that, and briefing it makes it a second opinion from your own context rather than a first opinion from the reader's.
-
Its deletions apply. They land in the working tree and you stage them; you do not review them back into place. The user sees them in the commit diff, which is the human review point.
-
Its Misfiled list is input to Draft the body — a comment deleted for being design rationale is rationale the body now has to carry.
-
Where a comment survives, its Kept line names the misunderstanding it prevents; that belongs in neither the body nor the code.
-
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.
- 4d ago Changed · -2 lines fe996c382206
- 11d ago Changed · +3 lines 9880ed0d099e
- 1mo ago Changed · -9 lines 218dd63fb227
- 1mo ago Changed · +19 lines 94db1a86ae9f
- 1mo ago Changed · +4 lines bfa55d2421cc
- 1mo ago Changed · +11 lines 06236b02f59f
- 1mo ago Changed · +21 lines 2d7a256e2522
- 1mo ago First seen · 98 lines · 98 tokens per session scan A 90632d3a3d74
commit is a skill published in the GitHub repository juxt/claude-plugins (10 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 2,123 once invoked, about $0.0004 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 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.