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 Awish021/opencode --skill conventional-commitsgit clone --depth 1 https://github.com/Awish021/opencodeWrote 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/awish021/opencode/conventional-commits)<a href="https://agentmods.dev/skills/awish021/opencode/conventional-commits"><img src="https://agentmods.dev/badge/skills/awish021/opencode/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/awish021/opencode/conventional-commits"><img src="https://agentmods.dev/badge/skills/awish021/opencode/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.00014 | $0.00447 |
| Opus 5.5 | $0.00006 | $0.00179 |
| Sonnet 5.5 | $0.00003 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00045 |
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 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 Commits
What I do
- Capture the essence of the change in the git staging area
- Draft a commit message from the staged changes
When to use me
Use this when you want to commit the code changes that have been staged. Ask clarifying questions if some changes are unclear to you.
Format
type(scope): description
Types
- feat: new feature
- fix: bug fix
- docs: documentation
- style: change style of code
- refactor: code restructuring
- test: adding or changing tests
- chore: maintenance
- perf: improving performance
- ci: changing or adding CI steps
Guardrails
- A commit message contains ONLY plain text - no markdown, no code blocks, no formatting
- A commit message NEVER contains triple backticks (```) or any markdown code block syntax
- A commit message NEVER contains any emojis or special formatting markers that suggest AI generation
- A commit message is written in an imperative mood (e.g. "add" not "added")
- A commit message must appear 100% human-written with no hints of AI involvement
- A commit message MUST be title-only unless the change complexity absolutely requires additional context. When in doubt, use title-only.
When to Add a Body
Add a body ONLY when:
- The title cannot explain WHY the change was made
- Multiple independent changes are included in one commit
- Breaking changes need detailed explanation
- Complex migration steps are required
DO NOT add a body for:
- Simple refactors that the title clearly describes
- Single-file changes with obvious intent
- Documentation updates with clear scope
Common Mistakes to Avoid
WRONG: "feat(api): add user authentication Adds login functionality for users"
- Title already says it all, body is redundant
RIGHT: "feat(api): add user authentication"
- Clear, concise, no redundant body
Examples
chore(deps): update dependenciesfix(api): resolve authentication bugrefactor(database): optimize query performance
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 · 64 lines · 14 tokens per session scan A d08a387a9841
conventional-commits is a skill published in the GitHub repository Awish021/opencode (11 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 447 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-30.
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…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.