agentmods.dev

conventional-commit

A rule for writing Git commit messages in the Conventional Commits format, a shared structure that labels changes such as features, fixes, and documentation.

In plain words
What is it for?
Use it whenever code changes need to be committed, including checking the changes and identifying breaking changes.
Why use it?
It keeps commit history consistent and makes the kind of change clear to people and tools reading it.

Skill for Claude CodeCodex

359 2d ago A scan 47 tokens original MIT
View the source file termio-sh/termio
Install

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.

agentmods
npx agentmods add skills/termio-sh/termio/conventional-commit
Any agent
npx skills add termio-sh/termio --skill conventional-commit
Clone the repo
git clone --depth 1 https://github.com/termio-sh/termio

Made for: Claude Code, Codex.

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 994 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00047 $0.00994
Opus 5 $0.00023 $0.00497
Sonnet 5 $0.00009 $0.00199
Haiku 4.5 $0.00005 $0.00099

Measured 2d ago against content hash 541c89c425fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • commit — 92% identical, 6 lines differ
skills/conventional-commit/SKILL.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Conventional Commit

Generate commit messages following the Conventional Commits 1.0.0 specification.

Commit Message Structure

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Instructions

When the user asks to commit changes:

  1. Analyze the changes by running:

    • git status to see all modified/added/deleted files
    • git diff --staged to see staged changes
    • git diff to see unstaged changes
    • git log -5 --oneline to match the repository's commit style

  2. Determine the commit type (REQUIRED):

    Type Description SemVer
    feat New feature MINOR
    fix Bug fix PATCH
    docs Documentation only -
    style Formatting, no code change -
    refactor Code change, no feature/fix -
    perf Performance improvement -
    test Adding/updating tests -
    build Build system or dependencies -
    ci CI configuration -
    chore Other changes -

  3. Identify breaking changes:

    • Append "!" after type/scope for breaking changes: "feat!:" or "feat(api)!:"
    • Add "BREAKING CHANGE:" footer for detailed explanation
    • Breaking changes trigger MAJOR version bump

  4. Write the commit message:

    • Description MUST immediately follow the colon and space
    • Description is a short summary in imperative mood
    • Body MUST begin one blank line after description
    • Footers MUST begin one blank line after body

  5. Stage and commit:

    • Stage relevant files with git add
    • Create commit with the generated message
    • Show git status after to confirm success
    • DO NOT add any Claude Code references, co-author tags, or "Generated with" footers

Specification Rules

  • Type MUST be a noun (feat, fix, etc.)
  • Scope MUST be a noun in parentheses describing codebase section
  • Description MUST use imperative mood ("add" not "added")
  • Body is free-form, may have multiple paragraphs
  • Footer token MUST use - instead of spaces (except BREAKING CHANGE)
  • BREAKING CHANGE MUST be uppercase
  • NEVER include AI-generated markers, Claude Code references, or Co-Authored-By: Claude footers

Read the full file on GitHub · 137 lines

Changes

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.

  1. 2d ago First seen · 137 lines · 47 tokens per session scan A 541c89c425fe

Subscribe to this mod's changes

conventional-commit is a skill published in the GitHub repository termio-sh/termio (359 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 994 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-30.

Git and workflowWriting and docsadeagenticai-agentsclaude-codeclicodex
Related

Other skills, from other repositories

zh-output-example

Reviews Chinese skill documentation for publication readiness. Invoke when the user asks in Chinese to review a skill.

bytedance/deer-flow · 24 tokens

peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

the-open-agent/openagent · 17 tokens

powerpoint

Create designed, editable PowerPoint .pptx presentations with PptxGenJS. Use when the user asks to create, generate, update, or inspect a deck, slide deck, presentation, or .pptx file.

the-open-agent/openagent · 48 tokens

memory

Use durable BB memory when prior project knowledge or cross-project user preferences can improve the current task, and save durable new learning through the bb memory CLI.

get-bb/bb · 32 tokens

workflows

Execute a workflow script that orchestrates multiple subagents deterministically. Use when the user explicitly requests a workflow, multi-agent orchestration, parallel or sequential agent pipelines, structured agent outputs, or a durable background workflow run.

get-bb/bb · 47 tokens

argent-tv-interact

Control and inspect TV apps via argent — Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…

software-mansion/argent · 107 tokens