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 bnet47/codexicon --skill conventional-commitgit clone --depth 1 https://github.com/bnet47/codexiconWrote 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/bnet47/codexicon/conventional-commit)<a href="https://agentmods.dev/skills/bnet47/codexicon/conventional-commit"><img src="https://agentmods.dev/badge/skills/bnet47/codexicon/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/bnet47/codexicon/conventional-commit"><img src="https://agentmods.dev/badge/skills/bnet47/codexicon/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.00028 | $0.00266 |
| Opus 5.5 | $0.00011 | $0.00106 |
| Sonnet 5.5 | $0.00006 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00027 |
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
Conventional commit
Format:
type(scope): imperative summary
Allowed types: feat, fix, docs, refactor, test, chore, perf, ci, build, revert.
- Derive the scope from the behavior or module, not the ticket name.
- Use lowercase imperative wording with no trailing period.
- Keep the subject at or below 72 characters when practical.
- Add a body when motivation, migration, compatibility, or risk is not obvious from the diff.
- Add
BREAKING CHANGE:only for an intentional incompatible change.
Use the supplied change details, task scope, changed-path evidence, and verification results to draft a message even when nothing is staged. During Build, staging is outside the authority boundary; do not request it or treat its absence as missing input. During Ship, inspect the staged diff when one is available and report unrelated or unverified changes instead of inventing a broad message.
This skill does not stage files, create a commit, push, or open a PR unless the user explicitly requested those operations through $ship or an equivalent instruction.
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 Changed 854ff33caa6e
- 1mo ago First seen · 25 lines · 28 tokens per session scan A adda6a622fba
conventional-commit is a skill published in the GitHub repository bnet47/codexicon (5 stars, last pushed 20d ago), licensed MIT. It adds 28 tokens to every session and 266 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
oma-scm
Manage Git branches, merges, conflicts, commits, and release baselines. Use for repository history and change-management operations.
git-commit
A guided Git commit workflow that examines changes and creates a commit message using the Conventional Commits format, a shared style for labeling changes such as features, fixes, tests, or documentation.
gentle-ai-work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
precommit
Pre-commit checks — lint:fix -> build -> test.
next-step
Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.
precommit-fast
Quick pre-commit checks — lint:fix -> test.