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 fmind/dotfiles --skill conventional-commitgit clone --depth 1 https://github.com/fmind/dotfilesWrote 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/dotfiles/conventional-commit)<a href="https://agentmods.dev/skills/fmind/dotfiles/conventional-commit"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/conventional-commit/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/fmind/dotfiles/conventional-commit"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/conventional-commit.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.00031 | $0.00484 |
| Opus 5.5 | $0.00012 | $0.00194 |
| Sonnet 5.5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00048 |
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 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
Create Conventional Commit
Create a Conventional Commits message for the staged changes in this repository and commit them.
Workflow
- Inspect the staged state:
git diff --cached --name-only— staged files.git diff --cached --stat— diff stat.git diff --cached— full patch.
- If nothing is staged, say so and stop.
- Read the staged files or nearby context if the patch is ambiguous.
- Write one Conventional Commits subject:
- Form:
<type>(<scope>): <description>where<type>isfeat,fix,chore,docs,refactor,test,perf,ci,build,style, orrevert.<scope>is optional. - Imperative mood (
add, notadded). - Under 72 characters total.
- Precise scope when it helps; omit if it adds no signal.
- For a breaking change, append
!after the type/scope, e.g.feat(api)!: drop v1 endpoint.
- Form:
- Run
git commit -m "<subject>"with that exact subject, then read the short hash from the commit output (orgit rev-parse --short HEAD). - After success, print only these two lines:
Subject: <subject>
Commit: <hash>
- If the commit fails (pre-commit hook, no staged changes), show the failure briefly and stop. Do not amend.
Gotchas
- Keep the final response plain text and compact.
- Never run
git pushfrom this skill.
Documentation
- github-pull-request — open or update a PR after the branch has commits.
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 · 48 lines · 31 tokens per session scan A e394646c86ae
conventional-commit is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 484 once invoked, about $0.0001 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
git-delivery
Stage, commit, push, and release scoped changes with Conventional Commits; fix hook failures.
resolve-conflicts
Resolve Git merge or rebase conflicts by both sides' intent; verify the result.
github-repository
Set GitHub repo description, topics, merge policy, and security settings.
github-pull-request
Open, update, and verify GitHub pull requests.
commit
Describe and finalize work with jj-vcs — drafting a description for the current change, splitting mixed work into focused commits, and advancing to a clean working copy. Use when asked to commit, when finishing a unit of work, or when starting new work on top of undescribed changes.
git-worktree
Create Git branches, worktrees, or isolated snapshots of uncommitted work.