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/darellchua2/opencode-config-template/semantic-release-convention-skillnpx skills add darellchua2/opencode-config-template --skill semantic-release-convention-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/semantic-release-convention-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/semantic-release-convention-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/semantic-release-convention-skill.svg" alt="Measured on agentmods" 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.00037 | $0.03326 |
| Opus 5 | $0.00018 | $0.01663 |
| Sonnet 5 | $0.00007 | $0.00665 |
| Haiku 4.5 | $0.00004 | $0.00333 |
Grade A, and why
semantic-release-convention-skill 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 — 417 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I define the standardized conventions for the entire release pipeline from commit to deployment:
- Commit Message Convention: Conventional Commits format with types, scopes, and breaking change indicators
- PR Title Convention: PR titles must follow Conventional Commits format
- PR Label Rules: Every PR requires exactly one semver label (
major/minor/patch) as the version bump decision factor - Merge Strategy: Squash merge with conventional commit title and PR description as body
- Release Tag Convention: Branch-aware versioned tags with prerelease suffixes
- GitHub Actions Requirements: Four CI/CD workflows for enforcement
This is a governance skill - it defines conventions that other skills and agents MUST follow. It does not execute workflows itself.
When to use me
- When creating commit messages, PR titles, or release tags
- When determining version bump type for a PR
- When generating release tags for different branches
- When setting up GitHub Actions for release enforcement
- When any skill needs to know the correct convention for commits, PRs, or releases
Governed Skills
| Skill | What It Consumes |
|---|---|
git-semantic-commits |
Commit type definitions and format rules |
git-compact-commits |
Length budgets (72-char subject, 150-word body), semantic grouping strategy, commitlint config authority |
pr-creation-workflow |
PR title format, label mapping, merge conventions, JIRA image handling |
nextjs-pr-workflow |
Inherits via pr-creation-workflow |
git-issue-labeler |
Semver label definitions and detection |
changelog-python-cliff |
Changelog category structure from commit types |
version-bump-standard |
Release tag formats, branch-aware pre-release suffixes, workflow templates for dev/uat/main flow |
Consumed By
| Consumer | Type | Usage |
|---|---|---|
pr-workflow-subagent |
Agent | PR creation with release conventions |
ticket-plan-workflow-skill |
Skill | Version label assignment during ticket creation (primary direct load) |
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 · 417 lines · 37 tokens per session scan A df4f2f0079d6
semantic-release-convention-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 37 tokens to every session and 3,326 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-09-03.
Other skills, from other repositories
ship
Use when ready to ship code to remote — handles direct push to main and PR-based feature branch flows. Do NOT use for partial workflows like just committing or just pushing.
git-ship
自动化 Git 工作流一键发布助手，执行完整的「ship」流程： 基于最新 main 切新分支 → commit → 推送 → 创建 PR → squash merge → 回 main。 调用 ship 本身就是对完整流程的授权；自动推断分支名、commit message 和 PR 内容， 并主动解决 Git 冲突、测试、lint、类型检查、构建和 CI 失败，持续修复和重试， 直到改动成功合并。不要因可自行修复的失败暂停，只在认证、权限、仓库保护等 无法由当前环境解决的外部阻塞出现时请求用户介入。 仅在用户明确表达「ship」意图时触发，例如： 直接说「ship」「/ship」「git ship」 明确要求完整走完 git…
jig-conformance-audit
Use to check whether a repository's history actually followed the jig procedure: conventional squash subjects, Release-Grade trailers on unreleased work, version tag format and placement, the main/develop fast-forward invariant, and a committed rubric. Read-only, exits non-zero on violations, and runs in CI.
conformance-audit
Use to check whether a repository's history actually followed the jig procedure: conventional squash subjects, Release-Grade trailers on unreleased work, version tag format and placement, the main/develop fast-forward invariant, and a committed rubric. Read-only, exits non-zero on violations, and runs in CI.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
crew-commit
Canonical commit workflow for Gas Town crew members: pre-flight checks, branch creation, gt commit with agent identity, push, and PR creation. Use when ready to commit and submit work for review.