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/strands-compose/sdk-python/conventional-commitsnpx skills add strands-compose/sdk-python --skill conventional-commitsgit clone --depth 1 https://github.com/strands-compose/sdk-pythonWhat 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.00043 | $0.00584 |
| Opus 5 | $0.00022 | $0.00292 |
| Sonnet 5 | $0.00009 | $0.00117 |
| Haiku 4.5 | $0.00004 | $0.00058 |
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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventional Commits
Turn a description of a code change into a commit message that follows the Conventional Commits standard.
When to use
Activate when the user asks for a commit message, or hands you a change summary or diff and wants it phrased for git.
Format
<type>(<optional scope>): <short summary>
<optional body>
<optional footer>
- type — one of
feat,fix,docs,refactor,test,perf,build,ci,chore. - scope — the area touched, e.g.
(api),(auth). Optional. - summary — imperative mood, lowercase, no trailing period, 72 characters or fewer.
- body — what changed and why, wrapped near 72 characters. Optional.
- footer —
BREAKING CHANGE: ...and issue refs likeCloses #123. Optional.
Steps
- Choose the single
typethat best fits the change. If it does more than one thing, suggest splitting the commit. - Add a
scopeonly when it clarifies where the change lives. - Write the summary in the imperative ("add", not "added" or "adds").
- Add a body only when the why is not obvious from the summary.
- Record breaking changes in the footer with
BREAKING CHANGE:and a short migration hint.
Examples
Input: "added pagination to the users list endpoint"
feat(api): add pagination to the users list endpoint
Input: "fixed a crash when the config file is missing; now we fall back to defaults"
fix(config): fall back to defaults when the config file is missing
A missing config previously raised at startup. Loading now logs a warning
and uses the built-in defaults instead.
Input: "stopped reading the AWS_REGION env var; region now comes from config"
refactor(config): drop the AWS_REGION env var in favor of a region field
BREAKING CHANGE: AWS_REGION is no longer read. Set `region:` in your model
config instead.
Edge cases
- Reverting a commit — use
revert: <original summary>and put the reverted hash in the body. - Several unrelated changes — recommend separate commits rather than one mega-commit.
- No obvious type — ask what the change is meant to accomplish before guessing.
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 · 72 lines · 43 tokens per session scan A 8471928cd675
conventional-commits is a skill published in the GitHub repository strands-compose/sdk-python (6 stars, last pushed 17d ago), licensed Apache-2.0. It adds 43 tokens to every session and 584 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
commit
Generate a commit message and description for staged/unstaged changes.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
dispatch
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…
maestro-improve
Turn filed lessons into the smallest doctrine edit - group pending lessons by target, make one commit per target carrying their evidence ids, mark each lesson processed by that commit or answered with the reason it was rejected, and hand back for the challenge lane.
ak-dev-code-quality
Code quality standards, formatting, commit conventions, and PR workflow for Agent Kernel development. Use this skill when making contributions, formatting code, writing commit messages, or preparing pull requests.
git-workflow
Branching strategies, conventional commits, PR templates, and merge vs rebase guidance. Activate when starting features, creating PRs, or managing releases.