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 Magnus-Gille/claude-skills --skill commitgit clone --depth 1 https://github.com/Magnus-Gille/claude-skillsWrote 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/magnus-gille/claude-skills/commit)<a href="https://agentmods.dev/skills/magnus-gille/claude-skills/commit"><img src="https://agentmods.dev/badge/skills/magnus-gille/claude-skills/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/magnus-gille/claude-skills/commit"><img src="https://agentmods.dev/badge/skills/magnus-gille/claude-skills/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.00037 | $0.00724 |
| Opus 5 | $0.00018 | $0.00362 |
| Sonnet 5 | $0.00007 | $0.00145 |
| Haiku 4.5 | $0.00004 | $0.00072 |
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 2d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$commit - Standardized Git Commit
Create clean, well-documented git commits with safety checks.
Usage
$commit- Stage, review, and commit changes$commit <message>- Commit with a specific message (still runs safety checks)$commit amend- Amend the explicitly requested commit
Workflow
Step 1: Verify Author Identity
git config user.name
git config user.email
- The configured identity should be the user's intended name and email for this repository. If either is empty or unexpected (for example, a CI or bot identity), warn before proceeding.
- Do NOT silently fix it — the user should decide whether to update the config or commit under the current identity.
Step 2: Review Changes
Run in parallel:
git status
git diff --stat
git diff --staged --stat
Present a summary:
- Files modified (staged vs unstaged)
- Files added/deleted
- Untracked files that might need staging
Stage specific task-owned files within the requested commit scope. Preserve unrelated staged and unstaged changes; ask only when ownership or scope is unclear. Inspect the exact staged diff before committing, including any pre-existing staged content. Do not include unrelated staged content in this commit or unstage it without authorization.
Step 3: Security Check
Before committing, verify:
- No
.env,credentials.json,token.json, orclient_secret_*.jsonfiles are staged - No files in
secrets/are staged - No files with
key,secret, ortokenin the name are staged (unless they're clearly code files)
If any are found, warn and stop. Do not commit.
Step 4: Write Commit Message
If no message was provided, draft one:
- Use conventional commit format:
type: description - Types:
feat,fix,docs,refactor,test,chore,style - Keep the first line under 72 characters
- Add a body paragraph if the change is non-trivial
- Always end with:
Co-Authored-By: Codex <[email protected]>
Show the proposed message and staged diff summary, then commit under the existing request. Ask again only when the user required message approval or a material scope decision remains.
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.
- 2d ago Changed · -3 lines · +18 tokens per session 7622b7fea288
- 8d ago First seen · 88 lines · 19 tokens per session scan A 60529e901476
commit is a skill published in the GitHub repository Magnus-Gille/claude-skills (5 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 724 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-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-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…