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/fmind/dot/conventional-commitnpx skills add fmind/dot --skill conventional-commitgit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/conventional-commit)<a href="https://agentmods.dev/skills/fmind/dot/conventional-commit"><img src="https://agentmods.dev/badge/skills/fmind/dot/conventional-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 | $0.00031 | $0.00584 |
| Opus 5 | $0.00015 | $0.00292 |
| Sonnet 5 | $0.00006 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
conventional-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.
What it actually says
Conventional Commit
Turn the staged changes into one Conventional Commits subject and commit them; git-add-commit-push owns staging, hook healing, and pushing.
Workflow
-
Inspect the staged state; if nothing is staged, say so and stop:
git diff --cached --name-only # staged files git diff --cached --stat # diff stat git diff --cached # full patch -
Read context only when the patch alone is ambiguous: the staged files and their neighbors.
-
Write one subject as
<type>(<scope>): <description>:<type>isfeat,fix,chore,docs,refactor,test,perf,ci,build,style, orrevert;<scope>is optional and used only when it adds signal.- Imperative mood (
add, notadded), under 72 characters in total. - Breaking change: append
!after the type or scope, e.g.feat(api)!: drop v1 endpoint.
-
Commit with that exact subject and read the short hash from the output (or
git rev-parse --short HEAD):git commit -m "<subject>" -
Report only these two lines after success:
Subject: <subject> Commit: <hash> -
Stop on failure (pre-commit hook, nothing staged): show the failure briefly; do not amend.
Gotchas
- No push: this skill never runs
git push; git-add-commit-push does.
Documentation
- Conventional Commits
- Companion skills: feature-branch (branch first), git-add-commit-push (stage, commit, push), github-pull-request (open the PR).
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 · 54 lines · 31 tokens per session scan A 391ec59e905f
conventional-commit is a skill published in the GitHub repository fmind/dot (4 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 584 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
lefthook
Canonical lefthook git-hooks setup — pre-commit (format, check, secret scan) and pre-push (test), each delegating to mise run tasks. Use when configuring or debugging git hooks.
git-add-commit-push
Stage, commit (Conventional Commits), and push in one flow, auto-healing lefthook pre-commit and pre-push failures. Use when committing and pushing work end-to-end.
conventional-commit
Write a Conventional Commits subject for the staged changes and commit them. Use when committing staged work with a typed, scoped message.
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.