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 lijinnair/claude-code-skillforge --skill formatting-commitsgit clone --depth 1 https://github.com/lijinnair/claude-code-skillforgeWrote 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/lijinnair/claude-code-skillforge/formatting-commits)<a href="https://agentmods.dev/skills/lijinnair/claude-code-skillforge/formatting-commits"><img src="https://agentmods.dev/badge/skills/lijinnair/claude-code-skillforge/formatting-commits/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/lijinnair/claude-code-skillforge/formatting-commits"><img src="https://agentmods.dev/badge/skills/lijinnair/claude-code-skillforge/formatting-commits.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.00068 | $0.00480 |
| Opus 5.5 | $0.00027 | $0.00192 |
| Sonnet 5.5 | $0.00014 | $0.00096 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
formatting-commits 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
Git Commit Formatting SOP
Execution Steps
Step 1: Gather Staged Changes
If the user has not provided a description, run:
!`git diff --staged`
to capture the actual code changes as context.
Step 2: Classify the Change Type
Determine the correct Conventional Commits type based on the diff or description:
feat— A new featurefix— A bug fixdocs— Documentation only changesstyle— Formatting, missing semi-colons, etc.refactor— Code change that is neither a fix nor a featurechore— Build process, dependency updatestest— Adding or fixing tests
Step 3: Extract Scope
Identify the affected module, component, or file area (e.g., auth, api, ui). Use (scope) in the commit header.
Step 4: Write the Commit Message
Compose the full commit message following this structure:
<type>(<scope>): <short imperative summary under 72 chars>
<optional body: what changed and why, not how>
<optional footer: BREAKING CHANGE: ... or Closes #issue>
Examples:
Input: Added user authentication with JWT tokens Output:
feat(auth): implement JWT-based authentication
Add login endpoint and token validation middleware
Input: Fixed bug where dates displayed incorrectly in reports Output:
fix(reports): correct date formatting in timezone conversion
Use UTC timestamps consistently across report generation
Input: Updated dependencies and refactored error handling Output:
chore: update dependencies and refactor error handling
- Upgrade lodash to 4.17.21
- Standardize error response format across endpoints
Step 5: Deliver
Output the final commit message in a single code block, ready to copy-paste into the terminal.
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 · 69 lines · 68 tokens per session scan A e413718271f0
formatting-commits is a skill published in the GitHub repository lijinnair/claude-code-skillforge (1 stars, last pushed 7mo ago), licensed MIT. It adds 68 tokens to every session and 480 once invoked, about $0.0003 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-31.
Other skills, from other repositories
commit-messages
Write git commit messages and pull request titles in the WARP format used by the swarms repo.
setup-pre-commit
A setup for Husky pre-commit checks in a JavaScript or TypeScript repository. A pre-commit hook runs automatically before a Git commit and can format staged files, check types, and run tests.
setup-pre-commit
A setup guide for Git pre-commit checks, which run automatically before a commit is created. It configures Husky, lint-staged, Prettier, type checking, and tests in a repository.
commit-and-push
Create a well-formatted git commit and push to remote repository.
effect-ledger
Record an effect, sign an effect, reconcile an effect or check "did this PR merge" through the signed AIWG effect ledger, using one aiwg effect command with scriptable exit codes.
customize-contribute-back
Contribute a user's AIWG customization back upstream as a PR — reviews for general applicability, creates branch, opens PR.