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 agentmods add commands/sgaunet/claude-plugins/commitgit clone --depth 1 https://github.com/sgaunet/claude-pluginsWhat 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 | $0.00010 | $0.00929 |
| Opus 5 | $0.00005 | $0.00464 |
| Sonnet 5 | $0.00002 | $0.00186 |
| Haiku 4.5 | $0.00001 | $0.00093 |
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 yesterday.
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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Command
Generate a git commit for staged changes using conventional commit format. This command 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.
- yesterday First seen · 105 lines · 10 tokens per session scan A 4045036f012d
commit is a command published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 6d ago), licensed MIT. It adds 10 tokens to every session and 929 once invoked, about $0.0001 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-30.
Other commands, from other repositories
security-audit-static
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.
performance-audit-static
Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact.
sprint
Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes.
document-app
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply.
analyze-test
Analyze A/B test results — statistical significance, sample size validation, and ship/extend/stop recommendations.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.