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 sgaunet/claude-plugins --skill commitgit clone --depth 1 https://github.com/sgaunet/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/sgaunet/claude-plugins/commit)<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/commit"><img src="https://agentmods.dev/badge/skills/sgaunet/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/sgaunet/claude-plugins/commit"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/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.00010 | $0.00943 |
| Opus 5.5 | $0.00004 | $0.00377 |
| Sonnet 5.5 | $0.00002 | $0.00189 |
| Haiku 4.5 | $0.00001 | $0.00094 |
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 21d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit
Generate a git commit for staged changes using conventional commit format. This skill analyzes the current git state, creates an appropriate commit message, and executes the commit with user permission.
Process
-
Analyze Changes: Check git status and diff to understand what's being committed:
git status git diff --staged -
Generate Commit Message: Create a conventional commit message based on the changes
-
Request Permission: Always ask user confirmation before executing the commit
-
Execute Commit: Run the git commit command. NEVER append
Co-Authored-By,Generated-by, or any attribution trailer. The commit message must contain ONLY the conventional commit message — no trailers, no co-authorship lines.
Conventional Commit Format
Structure: <type>[optional scope]: <description>
Types
- feat: New feature or functionality
- fix: Bug fix or error correction
- docs: Documentation changes only
- style: Code formatting, missing semicolons, whitespace (no logic changes)
- refactor: Code restructuring without changing external behavior
- test: Adding, updating, or fixing tests
- chore: Maintenance tasks, dependency updates, build changes
- perf: Performance improvements
- ci: CI/CD pipeline changes
- build: Build system or external dependency changes
- revert: Reverting a previous commit
Scope Guidelines
- Optional: Component, module, or area affected
- Format: Lowercase, no spaces (use hyphens if needed)
- Examples:
auth,api,ui,database,user-management
Description Rules
- Tense: Present tense, imperative mood ("add" not "adds" or "added")
- Case: Lowercase start
- Length: Under 50 characters for the subject line
- Punctuation: No period at the end
- Clarity: Be specific and concise
Examples
git commit -m "feat(auth): add oauth2 integration"
git commit -m "fix(api): handle null response in user endpoint"
git commit -m "docs: update installation instructions"
git commit -m "refactor(database): simplify connection pooling"
git commit -m "test(auth): add unit tests for login validation"
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.
- 21d ago First seen · 107 lines · 10 tokens per session scan A 9128442edecb
commit is a skill published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 7d ago), licensed MIT. It adds 10 tokens to every session and 943 once invoked, about $0.0000 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-25.
Other skills, from other repositories
commit-message
Use ANY time the user signals they want to commit staged changes — including bare "commit", "/commit", "commit this", "commit these changes", "let's commit", "make a commit", "git commit", "write a commit message", "make a conventional commit", "use conventional commits", or any equivalent phrasing in context (e.g.…
committing-staged-with-message
Generate commit message for staged changes, pause for approval, then commit. Stage files first with git add, then run this skill.
detecting-secrets
Detect hardcoded secrets, API keys, tokens, and credentials in code and git history. Use when auditing for leaked secrets or before publishing code.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
version-bump
This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump versions, prepare a release, or increment version numbers across the repository.