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 skills/versoxbt/claude-initial-setup/commit-conventionsnpx skills add VersoXBT/claude-initial-setup --skill commit-conventionsgit clone --depth 1 https://github.com/VersoXBT/claude-initial-setupWhat 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.00057 | $0.01202 |
| Opus 5 | $0.00028 | $0.00601 |
| Sonnet 5 | $0.00011 | $0.00240 |
| Haiku 4.5 | $0.00006 | $0.00120 |
Grade A, and why
commit-conventions 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventional Commits
Standard format for commit messages that enables automated changelogs, semantic versioning, and clear project history.
When to Use
- Writing any git commit message
- Reviewing commit history for consistency
- Setting up commit linting (commitlint, husky)
- Generating changelogs or release notes
- Any time
git commitis about to be executed
Core Patterns
Commit Message Structure
Follow this exact format:
<type>(<optional-scope>): <description>
<optional body>
<optional footer(s)>
The first line (subject) must be under 72 characters. Use imperative mood ("add feature" not "added feature" or "adds feature").
# Simple commit
git commit -m "feat: add user registration endpoint"
# With scope
git commit -m "fix(auth): prevent token refresh race condition"
# With body and footer
git commit -m "feat(api): add pagination to list endpoints
Implement cursor-based pagination for all collection endpoints.
Default page size is 20, max is 100.
Closes #142"
Commit Types
| Type | When to Use | Triggers Version Bump |
|---|---|---|
feat |
New feature or capability | MINOR (0.X.0) |
fix |
Bug fix | PATCH (0.0.X) |
refactor |
Code change that neither fixes nor adds | None |
docs |
Documentation only | None |
test |
Adding or fixing tests | None |
chore |
Maintenance, deps, tooling | None |
perf |
Performance improvement | None |
ci |
CI/CD configuration changes | None |
style |
Formatting, whitespace, semicolons | None |
build |
Build system or external deps | None |
revert |
Reverts a previous commit | Depends |
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 First seen · 149 lines · 57 tokens per session scan A a5c700f33035
commit-conventions is a skill published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 1,202 once invoked, about $0.0003 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…
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…