Borrowing it
Nothing to install: this file belongs to 0xku/kon. 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/0xku/kon/main/.agents/skills/kon-release-publish/SKILL.mdgit clone --depth 1 https://github.com/0xku/konWrote 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/0xku/kon/kon-release-publish)<a href="https://agentmods.dev/skills/0xku/kon/kon-release-publish"><img src="https://agentmods.dev/badge/skills/0xku/kon/kon-release-publish/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/0xku/kon/kon-release-publish"><img src="https://agentmods.dev/badge/skills/0xku/kon/kon-release-publish.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.00025 | $0.00996 |
| Opus 5 | $0.00013 | $0.00498 |
| Sonnet 5 | $0.00005 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade C, and why
kon-release-publish scanned grade C 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 11d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- `rm -rf dist && uv build` How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kon Release + PyPI Publish
Use this skill when the user asks to cut a new Kon version, tag it, publish to PyPI, and/or create a GitHub release.
Inputs to confirm
- Target version (example:
0.2.1) - Base range for notes (usually previous tag, example:
v0.2.0..HEAD) - Whether to push
main - Whether to publish to PyPI now
- Whether to create GitHub release now
Versioning requirement
- Kon's update check only supports strict numeric
MAJOR.MINOR.PATCHversions such as0.2.7and0.3.0. - Do not cut releases with PyPI/PEP 440 prerelease or suffix forms like
0.3.0rc1,0.3.0b1,0.3.0.post1, or0.3.0.dev1unless the update-check logic is updated first. - Even though PyPI commonly allows those formats, Kon releases should continue following plain
X.Y.Zso update detection stays correct.
Files to bump
pyproject.toml→[project].versionsrc/kon/version.py→ fallbackVERSION = "..."uv.lock→ local package version block
Release workflow
-
Preflight
git status --short --branchmust be clean (or confirm with user)git tag --listandgit log --oneline <prev_tag>..HEADto summarize changes
-
Update CHANGELOG.md
- Replace the
## [Unreleased]section's- No changes yet.with a new versioned heading:## <version> - YYYY-MM-DD - Use
git log --oneline <prev_tag>..HEADto categorize changes into### Added,### Changed,### Fixedsections - Credit external contributors with
- @username - Commit message:
docs: update changelog for <version>
- Replace the
-
Version bump
- Update version in all 3 files above
-
Quality gates
uv run ruff format .uv run ruff check .uv run pyright .uv run pytest
-
Commit
- Commit message:
build: bump version to <version>
- Commit message:
-
Tag
- Annotated tag:
git tag -a v<version> -m "v<version> ..." - Include concise "changes since previous tag" bullets
- Annotated tag:
-
Push
git push origin maingit push origin v<version>
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.
- 11d ago First seen · 99 lines · 25 tokens per session scan C e35c406d4cfa
kon-release-publish is a skill published in the GitHub repository 0xku/kon (353 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 996 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.