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 dentiny/kon --skill commit-messagegit clone --depth 1 https://github.com/dentiny/konWrote 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/dentiny/kon/commit-message)<a href="https://agentmods.dev/skills/dentiny/kon/commit-message"><img src="https://agentmods.dev/badge/skills/dentiny/kon/commit-message/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/dentiny/kon/commit-message"><img src="https://agentmods.dev/badge/skills/dentiny/kon/commit-message.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.00050 | $0.00626 |
| Opus 5.5 | $0.00020 | $0.00250 |
| Sonnet 5.5 | $0.00010 | $0.00125 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
commit-message 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.
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.
Commit Message
Consumers: any task that drafts a commit message after a successful run.
Core principles (always): follow skills/core-principles — subject states user impact concisely; no motivation paragraphs or padding.
Subject rules
- One line, ≤ 70 chars, user-impact framing — what changes for the user, not which files were touched
- Verb-first: "Add", "Fix", "Allow", "Reject", "Block"
- No file names in the subject: "Refactor auth.py" is bad; "Reject empty emails at signup" is good
- Match existing style: if the repo uses Conventional Commits (
type(scope): subject), keep that format; otherwise freeform- Detect Conventional Commits:
pyproject.tomlhas[tool.commitizen], or.cz.toml/commitlint.config.jsexists
- Detect Conventional Commits:
Bad → Good
| Bad | Good |
|---|---|
update auth.py and tests |
Reject empty emails before hashing |
fix bug |
Stop retry storm on 5xx from upstream |
address review comments |
Enforce non-empty email at signup |
Body rules
The body is for the future bisecting engineer, not the current reviewer:
- ≤ 3 sentences total, or equivalent compact bullets
- Cover only: what changed at the user-impact level, breaking-change pointers, irreplaceable invariants
- Cut: "why the problem existed", motivation paragraphs, "why we picked X over Y" — all of that belongs in the PR description
- If the subject is already complete and nothing durable remains to add, omit the body
Output format
<subject — one line, ≤70 chars, user-impact>
<body — ≤3 sentences; omit entirely if nothing durable to add>
Provide raw text to the caller — do not wrap in a code fence by default (breaks piping to git commit -F -).
When presenting to the user as a readable deliverable, wrap in a single fenced code block.
No git commit — ever
Agents never run git commit or git push. The skill produces text only.
Present the draft in a fenced code block so the user can copy it and run:
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 · 67 lines · 50 tokens per session scan A 40cacd7ca3f3
commit-message is a skill published in the GitHub repository dentiny/kon (3 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 626 once invoked, about $0.0002 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.