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 alexeyshishin/as-skill --skill git-conventional-commitsgit clone --depth 1 https://github.com/alexeyshishin/as-skillWrote 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/alexeyshishin/as-skill/git-conventional-commits)<a href="https://agentmods.dev/skills/alexeyshishin/as-skill/git-conventional-commits"><img src="https://agentmods.dev/badge/skills/alexeyshishin/as-skill/git-conventional-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/alexeyshishin/as-skill/git-conventional-commits"><img src="https://agentmods.dev/badge/skills/alexeyshishin/as-skill/git-conventional-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.00086 | $0.01170 |
| Opus 5 | $0.00043 | $0.00585 |
| Sonnet 5 | $0.00017 | $0.00234 |
| Haiku 4.5 | $0.00009 | $0.00117 |
Grade A, and why
git-conventional-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 9d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-conventional-commits — Conventional Commit message for the current diff
Goal: instead of the user writing the commit message themselves, you analyze the diff and build a message following the convention in ~/.claude/rules/git-conventions.md.
Before starting, read ~/.claude/rules/git-conventions.md — it has the full list of allowed type values, the scope format, and the principles.
Step 1. Gather context
Run:
git status --short— see what's changedgit diff --staged(if there's staged content) orgit diff(if not) — the content of the changesgit log --oneline -10— the style of previous commits in the project (especially the language: Russian/English)
If staged is empty and unstaged is also empty — tell the user and stop.
Step 2. Determine the type
Read the diff and decide:
| diff shows | type |
|---|---|
| a new file with functionality, a new endpoint, a new feature | feat |
| a logic fix so a bug no longer reproduces | fix |
| move/rename/simplify with no behavior change | refactor |
| performance improvement only | perf |
only .md, code comments |
docs |
| only tests added or fixed | test |
package.json, go.mod, requirements.txt, Dockerfile, CI configs |
build or ci |
| dependencies, tooling versions | chore(deps) |
| revert of a previous commit | revert |
If the diff is mixed (e.g. both fix and refactor) — stop and suggest the user split it into several commits. Don't write "feat: fixed a bug and refactored" — that's an anti-pattern.
Step 3. Determine the scope (optional)
Scope — a short name for the module/folder/SDK. Heuristic:
- if all files are under one top-level folder (
src/auth/,sdk-go/,cli/) — scope = that folder's name - if 2-3 files in different folders are touched — scope can be omitted
- if one specific component is fixed (
UserCard.tsx) — scope = the component name in kebab-case
Step 4. Write the subject
- 50-72 characters
- present-tense verb, no capital letter, no trailing period
- if the project's commits are in Russian — write in Russian, if in English — write in English (check
git log) - the subject describes what changed, not "what I did"
What ships with it
1 file 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.
- 9d ago First seen · 110 lines · 86 tokens per session scan A 7e83420f9456
git-conventional-commits is a skill published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 21d ago), licensed MIT. It adds 86 tokens to every session and 1,170 once invoked, about $0.0004 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
pwp-bootstrap
New project initialization protocol — from empty directory to production-ready foundation in one session. Use this skill whenever the user wants to start a new project, initialize a repo, scaffold an application, or set up a codebase from scratch. Also use when they say 'new project', 'start fresh', 'initialize a…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). Verify, commit. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to…
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
ship
Commit, push, and optionally create or update a PR for the current staged changes. Use when the user asks to "ship", "ship it", "ship changes", "commit push and PR", or "ship this".
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
git-flow
Use this skill when proposing, reviewing, or troubleshooting git commits, branches, pull requests, or merge strategies in a WrongStack project session. Triggers: user mentions "commit", "branch", "PR", "merge", "rebase", "stash", "diff".