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/version-bump-standard-skillnpx skills add darellchua2/opencode-config-template --skill version-bump-standard-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/version-bump-standard-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/version-bump-standard-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/version-bump-standard-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.00043 | $0.03149 |
| Opus 5 | $0.00022 | $0.01574 |
| Sonnet 5 | $0.00009 | $0.00630 |
| Haiku 4.5 | $0.00004 | $0.00315 |
Grade A, and why
version-bump-standard-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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Bump Standard
What I do
I ensure consistent version bumping and release workflows across all CanvasTekk repositories. I enforce the dev → uat → main branch flow with PR-label-driven semantic versioning.
When to use me
Use this skill when you need to:
- Set up or audit a repository's release workflow
- Standardize version bumping across repos
- Create or update
.github/workflows/bump-version-and-push-tag.yml - Configure branch protection rules for dev/uat/main
- Create enforcement workflows for branch promotion
- Attach audit bundles to production releases
- Onboard a new repo to the CanvasTekk release standard
The Standard
Branch Flow
feature branch
│
▼
dev ──────► auto-deploy dev, tag: vX.Y.Z-dev.N
│
│ PR: dev → uat (1 review, enforce-dev-to-uat check)
▼
uat ──────► auto-deploy uat, tag: vX.Y.Z-uat.N
│
│ PR: uat → main (1 review, enforce-uat-to-main check, label: patch/minor/major)
▼
main ─────► deploy prod, tag: vX.Y.Z (clean), GitHub Release + audit bundle
No prod branch. main is the production branch.
Version Tag Format
| Branch | Tag Format | Pre-release | Example |
|---|---|---|---|
| dev | vX.Y.Z-dev.N |
Yes | v1.40.0-dev.3 |
| uat | vX.Y.Z-uat.N |
Yes | v1.40.0-uat.1 |
| main | vX.Y.Z |
No (latest) | v1.40.0 |
Version Bump Determination
For main (production releases):
The PR label determines the bump type:
| PR Label | Bump Type | Example | When to use |
|---|---|---|---|
patch |
Patch | v1.40.0 → v1.40.1 | Bug fixes, config changes, infra tweaks |
minor |
Minor | v1.40.0 → v1.41.0 | New features, new resources, additive changes |
major |
Major | v1.40.0 → v2.0.0 | Breaking changes, destructive migrations |
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 347 lines · 43 tokens per session scan A 91b2fe442dcd
version-bump-standard-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 43 tokens to every session and 3,149 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
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
tutti-app-release
Set up, review, run, or debug external repositories that publish a Tutti workspace app through the reusable Tutti App Release GitHub Actions workflow. Use for caller workflows, tutti.app.json manifests, @tutti-os/app-release-tools, S3/CloudFront release hosting, latest.json, versions.json, catalog.json, catalog-only…
publish
Publish the Octop Python package: cut a release branch from develop, bump version, update CHANGELOG, open a PR to main; after merge, Actions tag on main (PyPI / Docker Hub + GHCR) and sync main into develop. Use when the user asks to publish, release, bump version, cut a release, or run /publish.
seed-snapshot-release
Drives the snapshot-release flow for the current branch's PR. Posts a /snapshot comment on the PR if one isn't already there (with confirmation), waits for the Continuous Releases workflow to finish, and reports the tarball URLs from the resulting 📦 Snapshot Release comment. Use for both triggering and waiting …
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.