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 devantler-tech/agent-plugins --skill conventional-releasegit clone --depth 1 https://github.com/devantler-tech/agent-pluginsWrote 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/devantler-tech/agent-plugins/conventional-release)<a href="https://agentmods.dev/skills/devantler-tech/agent-plugins/conventional-release"><img src="https://agentmods.dev/badge/skills/devantler-tech/agent-plugins/conventional-release/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/devantler-tech/agent-plugins/conventional-release"><img src="https://agentmods.dev/badge/skills/devantler-tech/agent-plugins/conventional-release.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.00088 | $0.02020 |
| Opus 5.5 | $0.00035 | $0.00808 |
| Sonnet 5.5 | $0.00018 | $0.00404 |
| Haiku 4.5 | $0.00009 | $0.00202 |
Grade A, and why
conventional-release 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventional Release
A widely-used release pattern: every PR is squash-merged, its title is a Conventional Commit, and an automated tool on the default branch reads the commit type to calculate the next SemVer tag, cut a release, and generate the changelog. No human writes a version number or a changelog entry by hand — the merge title is the release note, and the type is the bump.
Use this skill whenever you open or merge a PR into a repository that releases this way, or when you need to decide which version a change should produce.
How to tell a repo uses this pattern
Look for any one of:
- A release tool wired to run on push to the default branch:
semantic-release,release-please,mathieudutour/github-tag-action, or Changesets. - Branch protection that only allows squash merging (so the PR title is the sole commit message that reaches the default branch).
- A
CHANGELOG.mdthat is generated, or release notes grouped byFeatures/Bug Fixes. - A
commitlint/commitizenconfig, or CI that lints the PR title against the Conventional Commits spec.
If the repo squash-merges but releases manually, the title still matters for history and review — keep writing Conventional Commit titles, but the version step is the maintainer's.
The non-negotiable: the squash title is the only message that survives
With squash merging, GitHub collapses every commit on the branch into one commit on the default branch, and that commit's message defaults to the PR title. The release tool reads that message. So:
- The individual commits on your branch do not drive the release — only the final squash message does. Tidy WIP commits are fine; the PR title is what counts.
- The PR title MUST be a single valid Conventional Commit line. A title like
[fix] thingorWIP: thingorUpdate READMEeither yields no release, the wrong bump, or a corrupted changelog entry. - Never put a bracketed prefix, ticket id, or label in the title (
[infra],JIRA-123:,(wip)). Attribution belongs in labels and the branch name, never the title — a prefix before the type breaks the parser and pollutes the release notes.
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 · 158 lines · 88 tokens per session scan A 299146d7facf
conventional-release is a skill published in the GitHub repository devantler-tech/agent-plugins (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 88 tokens to every session and 2,020 once invoked, about $0.0004 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
version-bump
This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump versions, prepare a release, or increment version numbers across the repository.
slack-changelog
Turns what changed in a release into a Slack changelog a non-technical audience can read: filtered to what they would actually notice, one bullet per idea, plain language, no code vocabulary. Works out the scope itself across however many repositories sit in the working directory (a project can span several…
changelog-assembly
This skill should be used when the user mentions "changelog", "release notes", "keep a changelog", "conventional commits", "commit message", "what changed", or "release summary". Provides a standardized methodology to turn raw, possibly non-conventional git history into human-readable changelogs and release notes.
release
Draft, prepare, or publish a GitHub or GitLab release. Use when the user asks for release notes, wants to publish a release, or asks what changed since the last tag.
git-for-research-code
When the user wants to version-control optimization research code - small commits per experiment change, tags for paper result snapshots, .gitignore for solver logs, linking result tables to commit hashes, and branch strategy for risky refactors. Also use when the user mentions "git workflow," "version control…
claude-plugin-repo-ci-release
Wire up CI validation and automatic release-cutting for a Claude Code plugin or marketplace repo (a repo with a .claude-plugin/marketplace.json and plugins/). Adds two GitHub Actions — a structure validator that runs on every PR/push, and a release-on-version-bump job that cuts a GitHub Release whenever a VERSION file…