Borrowing it
Nothing to install: this file belongs to qiniu/go-sdk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/qiniu/go-sdk/master/.agents/skills/release-check/SKILL.mdgit clone --depth 1 https://github.com/qiniu/go-sdkWrote 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/qiniu/go-sdk/release-check)<a href="https://agentmods.dev/skills/qiniu/go-sdk/release-check"><img src="https://agentmods.dev/badge/skills/qiniu/go-sdk/release-check.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.00033 | $0.00350 |
| Opus 5 | $0.00016 | $0.00175 |
| Sonnet 5 | $0.00007 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
release-check 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 7d 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-check skill 检查版本号一致性。"
执行步骤
步骤 1：读取版本号
从 conf/conf.go 读取 const Version = "x.y.z"。
步骤 2：检查三处一致性
conf/conf.go—const Version = "<version>"CHANGELOG.md— 包含## <version>条目README.md— 包含require github.com/qiniu/go-sdk/v7 v<version>
步骤 3：输出结果
输出版本号和三处的匹配状态表格：
| 位置 | 期望 | 状态 |
|------|------|------|
| conf/conf.go | vX.Y.Z | ✓ 匹配 / ✗ 不匹配 |
| CHANGELOG.md | ## X.Y.Z | ✓ 匹配 / ✗ 不匹配 |
| README.md | require ... vX.Y.Z | ✓ 匹配 / ✗ 不匹配 |
如果有不一致，给出具体的修复建议。
系统规范（AGENTS.md）
执行本 skill 时同时遵守 AGENTS.md 中的系统规范；与本 skill 冲突时以本 skill 为准。
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.
- 7d ago First seen · 43 lines · 33 tokens per session scan A 1089d317edb5
release-check is a skill published in the GitHub repository qiniu/go-sdk (157 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 350 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-08-30.
Other skills, from other repositories
crawlkit
Maintain and release the crawlkit Go library, preserving downstream compatibility for gitcrawl, slacrawl, discrawl, and notcrawl.
pi-sync
Daily upstream-sync job for the pi Go port — fetch upstream pi, triage every change since the recorded pin, port what's in scope, verify idiomatic + parity via independent reviews, update the ledger, and push. Use for "sync with upstream", "porting job", or as the scheduled daily run.
goreleaser
Release Go binaries with GoReleaser: minimal .goreleaser.yaml, snapshot builds, tag-driven GitHub Actions release, cosign signing, ko images. Use when releasing a Go CLI.
google-cloud
Map Google Cloud product areas to the official google/skills cloud catalog and install what a task needs. Use for Google Cloud compute, data, AI, GKE, operations, or security work.
go-release
Release engineering for Go projects — GoReleaser v2 with version ldflags into an internal/version package, SBOMs and multi-arch container images, tag-triggered GitHub Actions releases, CI running build/vet/test -race/govulncheck with SHA-pinned actions, and Renovate coverage for gomod, tools, npm, and Actions. Use…
add-goreleaser-homebrew
Add GoReleaser configuration and a GitHub Actions release workflow to an existing Go CLI project with Homebrew tap publishing. Use when the user says "add goreleaser", "set up goreleaser", "add Homebrew tap publishing", "publish to Homebrew", "set up release workflow", "add release automation for Go", or wants a Go…