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 HelixDevelopment/code --skill conventional-commitgit clone --depth 1 https://github.com/HelixDevelopment/codeWrote 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/helixdevelopment/code/conventional-commit)<a href="https://agentmods.dev/skills/helixdevelopment/code/conventional-commit"><img src="https://agentmods.dev/badge/skills/helixdevelopment/code/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/helixdevelopment/code/conventional-commit"><img src="https://agentmods.dev/badge/skills/helixdevelopment/code/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.00013 | $0.00331 |
| Opus 5.5 | $0.00005 | $0.00132 |
| Sonnet 5.5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00001 | $0.00033 |
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
You are an expert release engineer. Produce a single Conventional Commits 1.0.0 message for the following change:
{{ARG.summary}}
Follow these rules exactly:
- Header line:
<type>[optional scope]: <description>typeis one of: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert.descriptionis imperative mood, lower-case, no trailing period, and at most 72 characters including the type and scope.
- Leave one blank line, then an optional body that explains what changed and why (not how), wrapped at 72 columns.
- If the change is backward-incompatible, add a
BREAKING CHANGE:footer (or a!after the type/scope in the header) describing the migration impact. - Reference related issues in a footer such as
Refs: #123when applicable.
Output only the commit message text, with no surrounding commentary, code fences, or explanation. The authoritative specification is {{ARG.spec_url}}.
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 · 31 lines · 13 tokens per session scan A 517dc60f7f35
conventional-commit is a skill published in the GitHub repository HelixDevelopment/code (2 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 331 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
release-notes
Draft a release note section from a commit range, grouped by what the reader gets.
kirocrew-prepare-pr
LOAD THIS FOR EVERY KIRO CREW PR you open or update (Kiro Crew repo only; not other repos or CRs). Runs the whole loop — issue + tier, commit, sync, squash, push, drive CI and AI review to green, fix a red main, arm auto-merge and watch it land (24h). 'push my changes' = prepare-only.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
vigilante-issue-implementation-on-gradle-multi-project
Implement a GitHub issue end-to-end when Vigilante dispatches work for a watched Gradle multi-project repository. Use the provided worktree, respect repository instructions, comment on the issue as work progresses, and report failures back to GitHub.
adk-git
Writes commit messages and pull request descriptions for the adk-python repository: Conventional Commits types and scopes, subject lines that say why a change was made, and the linked-issue and testing-plan sections the PR template requires. Use when writing or rewording a commit message, squashing commits before a…
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.