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 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/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/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="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.03741 |
| Opus 5.5 | $0.00015 | $0.01496 |
| Sonnet 5.5 | $0.00007 | $0.00748 |
| Haiku 4.5 | $0.00004 | $0.00374 |
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 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 — 440 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: feature/fix heads squash-merge with conventional commit title and PR description as body; long-lived heads merge with merge commits (head-class rule, same as
pr-merge-workflow-skill) - 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 |
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-creation-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.
- 1mo ago Changed · +24 lines 820232efc579
- 1mo ago Changed · -1 lines 0786a87c2951
- 1mo ago Changed 5d38b6e2a74d
- 1mo 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 1mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 3,741 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-09-03.
Other skills, from other repositories
git-ship
An automated Git release workflow that takes code changes through a branch, commit, pull request, review checks, squash merge, and return to the main branch. A pull request is a request to review and merge changes into a shared branch.
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.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.