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/atretyak1985/swarmery/git-commitnpx skills add atretyak1985/swarmery --skill git-commitgit clone --depth 1 https://github.com/atretyak1985/swarmeryWrote 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/atretyak1985/swarmery/git-commit)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/git-commit"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/git-commit.svg" alt="Measured on agentmods" 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.00042 | $0.00740 |
| Opus 5 | $0.00021 | $0.00370 |
| Sonnet 5 | $0.00008 | $0.00148 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
git-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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Generate conventional commit messages for staged changes: a <type>(<scope>): <subject> subject line, optional bullet body, optional BREAKING CHANGE: / Closes #N footer. Message generation only — no git operations are run. Scopes come from the project's .claude/project.json -> commitScopes.
Rules
- NEVER generate a message when staged files may contain secrets (
.env,*.populated.yaml,credentials.json,*.key,*.pem,*secret*). Refuse and instruct the user to unstage them — no exceptions, no confirmation prompt. - Subject: imperative mood, lowercase first word, no trailing period, max 72 characters, describing the user-visible change — never "update file X".
- One commit message per repo. Never combine scopes like
feat(app,infra). - Never use a deprecated scope — map it to its documented replacement from the project's
CLAUDE.md. - Add a
BREAKING CHANGE:footer whenever the change breaks existing APIs, CLI flags, or port assignments.
Resources
- Read
resources/procedure.mdwhen generating a message — the step-by-step procedure, inputs/outputs, security gate, self-check, and escalation rules. - Read
resources/format-reference.mdwhen picking type or scope — type/scope tables, subject rules, multi-scope handling, examples, failure modes. - Read
examples/commit-examples.mdfor additional worked examples (it may contain deprecated legacy scopes such asbe/fe/helm— always use currentcommitScopes).
How to use
What it does
Turns a staged diff into a conventional commit message: type chosen from what actually changed, scope mapped from the touched files to the project's own scope list, subject kept under 72 characters in imperative mood. It refuses outright when staged files look like they carry secrets.
When to use it
- You finished an implementation task, staged the files, and need the commit message.
- You squashed several commits and need one summary message.
- You want an existing message checked against project conventions.
- A change spans two repos and needs one correctly scoped message per repo.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 67 lines · 42 tokens per session scan A 74f59bb41568
git-commit is a skill published in the GitHub repository atretyak1985/swarmery (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 42 tokens to every session and 740 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-09-03.
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.…
claim
Acquire an exclusive lease on a fakoli-state task — pick from the ready queue, check for file conflicts, claim the task, and get a working git branch to commit into. Use this skill when ready to start work on an approved task.
commit-context
Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", "who wrote this", or wants context on a specific location in the codebase.
commit-history
List recent git commits linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", "list linked commits", or wants commits with their session context.
install-skill
Install a community skill pack into this fork from a GitHub repo and ship it as an auto-merged PR.
map-diff
Analyze the impact of staged git changes against the committed Cortex function knowledge graph — shows which downstream functions are affected before you commit.