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 gzb1128/opencode-plugin --skill releasegit clone --depth 1 https://github.com/gzb1128/opencode-pluginWrote 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/gzb1128/opencode-plugin/release)<a href="https://agentmods.dev/skills/gzb1128/opencode-plugin/release"><img src="https://agentmods.dev/badge/skills/gzb1128/opencode-plugin/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/gzb1128/opencode-plugin/release"><img src="https://agentmods.dev/badge/skills/gzb1128/opencode-plugin/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.00042 | $0.00619 |
| Opus 5.5 | $0.00017 | $0.00248 |
| Sonnet 5.5 | $0.00008 | $0.00124 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
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.
What it actually says
Release
项目使用 GitHub Actions + GoReleaser 自动构建发布。Agent 只需创建并推送 tag，CI 负责其余一切。
Workflow
-
确认工作区干净
git status --porcelain有未提交的变更则先处理，不要带着脏工作区发版。
-
确定版本号（遵循 SemVer）
git tag --sort=-v:refname | head -1 # 最新 tag git log <latest-tag>..HEAD --oneline # 新增 commits- 有新 feature → minor 版本 bump（如 v0.2.0 → v0.3.0）
- 只有 bugfix → patch bump（如 v0.2.0 → v0.2.1）
- 重大变更 → major bump
-
创建并推送 tag
git tag -a v0.3.0 -m "v0.3.0" git push origin v0.3.0 -
监控 CI
gh run list --workflow=release.yml --limit 3CI 会自动：运行测试 → GoReleaser 构建多平台二进制 → 创建 GitHub Release 并上传 artifacts + checksums。
禁忌
- 禁止本地运行
goreleaser release— 会上传 assets 到 GitHub，导致 CI 因 assets 冲突失败 - tag 必须打在 HEAD commit 上 — 否则 goreleaser 会报
tag was not made against commit校验失败
故障排查
tag 打错了位置
git tag -d v0.3.0
git push origin :refs/tags/v0.3.0
git tag -a v0.3.0 -m "v0.3.0"
git push origin v0.3.0
CI 因已有 release 失败
本地 goreleaser 提前创建了 release 导致冲突时：
gh release delete v0.3.0 --yes --cleanup-tag
git tag -a v0.3.0 -m "v0.3.0"
git push origin v0.3.0
查看 CI 日志
gh run view <run-id> --log-failed # 查看失败日志
gh run watch <run-id> --exit-status # 实时跟踪
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 · 71 lines · 42 tokens per session scan A ae3f4299d50f
release is a skill published in the GitHub repository gzb1128/opencode-plugin (2 stars, last pushed 24d ago), licensed MIT. It adds 42 tokens to every session and 619 once invoked, about $0.0002 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
last-tag
Show commits since the last tag in a formatted table. Use when user asks "what changed since last release", "commits since last tag", "last-tag", "what's new", or wants to see recent unreleased changes.
release
Prepare a version release — bump version files, commit, and tag. Just run /release with no arguments.
release-init
Detect project type and generate a tailored project-level /release skill. Run once per project to set up releasing.
release
Release any git repo that declares its version locations (no .rhiza/ needed) in one run — choose a version from a table, bump, regenerate the changelog, open a release PR, let the forge merge it once its checks pass, then tag the merged commit.
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.
rhiza-release
Release any git repo that declares its version locations (no .rhiza/ needed) in one run — choose a version from a table, bump, regenerate the changelog, open a release PR, let the forge merge it once its checks pass, then tag the merged commit.