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 Wang-Cankun/cankun-skills --skill skill-releasegit clone --depth 1 https://github.com/Wang-Cankun/cankun-skillsWrote 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/wang-cankun/cankun-skills/skill-release)<a href="https://agentmods.dev/skills/wang-cankun/cankun-skills/skill-release"><img src="https://agentmods.dev/badge/skills/wang-cankun/cankun-skills/skill-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/wang-cankun/cankun-skills/skill-release"><img src="https://agentmods.dev/badge/skills/wang-cankun/cankun-skills/skill-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.00073 | $0.01704 |
| Opus 5.5 | $0.00029 | $0.00682 |
| Sonnet 5.5 | $0.00015 | $0.00341 |
| Haiku 4.5 | $0.00007 | $0.00170 |
Grade A, and why
skill-release scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
compatibility: Requires `bun` + `curl` + the `skl` CLI. How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Release — converge the publish surfaces
A release is convergence, not a pipeline: every publish surface derives from
the skill's own files, so running this at any time is safe and idempotent.
Surfaces: the collection index (repo README.md), per-skill interface metadata
(agents/openai.yaml), the cankun.me/skills page,
and — rarely — a flagship repo.
Write boundary: this skill edits metadata surfaces only — frontmatter keys
(metadata.summary, compatibility:), agents/*.yaml, the index README, and
cankun-blog/app/data.ts.
The SKILL.md body belongs to the author: a content finding (weak description,
missing triggers) is a flag routed back, never an edit. The route starts at a
committed skill — moving a directory into skills/ is the author's (or skl's)
move, not this skill's.
The human-facing summary of a skill resolves through one chain, highest first:
- frontmatter
metadata.summaryinSKILL.md agents/openai.yaml→interface.short_description- first sentence of the frontmatter
description
Index prose is always derived through this chain, and convergence flows toward
the better text in either direction: when a row reads badly, fix the
skill's metadata.summary and reconverge; when existing row prose beats the
derived value, promote that prose into metadata.summary rather than
degrading the row.
1. Inventory
Enumerate skills/*/SKILL.md frontmatter (committed skills only — an untracked
skill is the author's work in progress, not a release candidate) and every row
of the README Collection table. Classify each skill and each row:
- matched — row text equals the derived summary (plus, when the skill
sets
compatibility:, that value appended verbatim); - stale — row exists but differs from that derived cell text;
- missing — committed skill with no row;
- orphan — row whose skill directory is gone.
Complete when: every committed skill and every row carries exactly one classification, shown to the user as a one-line-each table.
What ships with it
4 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.
- yesterday Changed · +1 lines 127d5767b41c
- 19d ago Changed · +12 lines 739cdbc5dd3b
- 2mo ago First seen · 131 lines · 73 tokens per session scan A a5241c7cee71
skill-release is a skill published in the GitHub repository Wang-Cankun/cankun-skills (2 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 1,704 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
release-skills
A release workflow for preparing and publishing a new version of a software project. A release is a named version that may include updated version files, release notes, tags, or a GitHub Release.
version-release
Choose and apply the correct semantic version bump for this repository. Use for every user-visible release, before merge when a change set should ship as patch, minor, or major, and whenever package/plugin/desktop version metadata must stay synchronized.
changelog-gen
A changelog generator that turns Git history into a version-by-version record of project changes. A changelog is a readable summary of new features, fixes, breaking changes, documentation, and other updates.
ship
Pre-release gate. Run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.
publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…