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 agentmods add skills/awish021/opencode/conventional-commitsnpx skills add Awish021/opencode --skill conventional-commitsgit clone --depth 1 https://github.com/Awish021/opencodeWhat 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 | $0.00014 | $0.00447 |
| Opus 5 | $0.00007 | $0.00224 |
| Sonnet 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 2d 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.
- 2d 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 2mo ago), licensed MIT. It adds 14 tokens to every session and 447 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…