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 jnMetaCode/skillet --skill conventional-commitsgit clone --depth 1 https://github.com/jnMetaCode/skilletWrote 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/jnmetacode/skillet/conventional-commits)<a href="https://agentmods.dev/skills/jnmetacode/skillet/conventional-commits"><img src="https://agentmods.dev/badge/skills/jnmetacode/skillet/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/jnmetacode/skillet/conventional-commits"><img src="https://agentmods.dev/badge/skills/jnmetacode/skillet/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.00032 | $0.00503 |
| Opus 5 | $0.00016 | $0.00251 |
| Sonnet 5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
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.
What it actually says
conventional-commits
Write the message from the diff, not from the conversation. The reader is a
stranger running git log in two years.
Procedure
- Read what is actually staged:
git diff --cached --statthen the diff itself. - Classify the change — pick ONE primary type:
featnew user-visible capability ·fixcorrects wrong behaviorrefactorno behavior change ·perffaster, same behaviordocs·test·build·ci·chore(only when nothing else fits)
- Scope = the subsystem a reader would filter by:
feat(parser): …. Omit if the repo doesn't use scopes (checkgit log --oneline -20and match style). - Subject line: imperative, lowercase, no period, ≤ 72 chars, and it must state the effect, not the activity — "fix: reject expired tokens" not "fix: update token check".
- Body (when the why isn't obvious): 1–3 sentences on why the change was needed and any non-obvious consequence. Wrap at 72. Never narrate the diff.
- Breaking change → footer
BREAKING CHANGE: <what breaks and the migration>, and add!after the type:feat(api)!: ….
Anti-patterns to reject
- One commit doing two unrelated things — split it (
git add -p). - "update", "misc fixes", "address comments" — say what changed.
- Restating the conversation ("as discussed…") — the log has no conversation.
- Explaining that the change is correct — that belongs in the PR, not the log.
Example
fix(ingest): treat mtime regressions as edits, not new files
Restored backups can move mtime backwards; we indexed those as fresh
documents, duplicating every chunk. Key on inode+path instead.
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 · 46 lines · 32 tokens per session scan A c4dec9ebd0a1
conventional-commits is a skill published in the GitHub repository jnMetaCode/skillet (1 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 503 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-08-31.
Other skills, from other repositories
conventional-commits
Write well-structured conventional commit messages. Use when committing code changes to ensure consistent, parseable commit history that enables automated changelogs and semantic versioning.
pod-init
Initialize CocoPlus project bundle in the current directory. Creates .cocoplus/ directory structure, copies all templates, initializes AGENTS.md, project.md, flow.json, and creates the initial git commit. Run this once per project before using any other CocoPlus command.
lean-review
CocoLean diff-scoped over-engineering audit — scans uncommitted git diff and applies five classification tags (delete/stdlib/native/yagni/shrink) to identify unnecessary surface area before commit.
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.
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
release-management
Automates GitHub releases with semantic versioning, changelog generation from merged PRs, and gh CLI integration. Supports draft, prerelease, and standard release workflows with task-tracked multi-phase execution. Use when creating releases, tagging versions, or publishing changelogs.