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 jeffh/claude-plugins --skill commitgit clone --depth 1 https://github.com/jeffh/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/jeffh/claude-plugins/commit)<a href="https://agentmods.dev/skills/jeffh/claude-plugins/commit"><img src="https://agentmods.dev/badge/skills/jeffh/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/jeffh/claude-plugins/commit"><img src="https://agentmods.dev/badge/skills/jeffh/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.00105 | $0.00611 |
| Opus 5.5 | $0.00042 | $0.00244 |
| Sonnet 5.5 | $0.00021 | $0.00122 |
| Haiku 4.5 | $0.00011 | $0.00061 |
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 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.
What it actually says
Commit Changes with Jujutsu
Write jj change descriptions for work done during this session, as if the user wrote them. NEVER add co-author information or Claude attribution.
Usage
- Describe the working copy (
@) and any undescribed parent commits. - If a revset is provided, describe only the specified revision(s), without splitting or modifying other commits.
Context expectations
When invoked from /jj:commit, the working-copy status, full diff, the undescribed-change list, recent log, and any configured commit template are already in context. Do not re-run them.
If invoked directly without that context, gather it first:
jj status --no-pager
jj diff --no-pager
jj log --no-pager -r 'trunk()..@ & description(exact:"")' -T 'change_id ++ "\n"'
Run jj diff --no-pager -r '<change_id>' for each undescribed commit, including parents. If a revset was provided, use jj log --no-pager -r '<revset>' and diff each commit instead.
Honor commit templates
If a commit-message template is configured — templates.draft_commit_description (jj) or commit.template (git) — follow its structure and section headings. Otherwise, match the style of recent log messages.
Message format
<type>: <subject>
[optional body]
Types: feat, fix, docs, refactor, test, chore, build
Rules:
- Subject: imperative mood, lowercase, no period, max 50 chars
- Body: wrap at 72 chars, explain WHY not just WHAT
- Group related changes logically
- Keep changes focused and atomic
Apply descriptions
jj describe -m "message" # current change (@)
jj describe -r <change_id> -m "msg" # specific revision
To split into multiple changes (only when no revset provided):
jj split -m "first message" path/to/files/
jj split -m "second message" more/files/
jj describe -m "remaining changes"
Show results
jj log --no-pager -r 'ancestors(@, 5)'
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 · 70 lines · 105 tokens per session scan A 0171439118fa
commit is a skill published in the GitHub repository jeffh/claude-plugins (12 stars, last pushed 19d ago), licensed Apache-2.0. It adds 105 tokens to every session and 611 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-30.
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.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
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…