Borrowing it
Nothing to install: this file belongs to syhily/kobato. 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/syhily/kobato/main/.agents/skills/release/SKILL.mdgit clone --depth 1 https://github.com/syhily/kobatoWrote 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/syhily/kobato/release)<a href="https://agentmods.dev/skills/syhily/kobato/release"><img src="https://agentmods.dev/badge/skills/syhily/kobato/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/syhily/kobato/release"><img src="https://agentmods.dev/badge/skills/syhily/kobato/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.01150 |
| Opus 5.5 | $0.00018 | $0.00460 |
| Sonnet 5.5 | $0.00009 | $0.00230 |
| Haiku 4.5 | $0.00005 | $0.00115 |
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 2mo 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Execute a Kobato release. The user provides two arguments:
$version— the version to release (e.g.6.3.0).$next_version— the next development version on develop (e.g.6.4.0-dev).
The entire release lifecycle runs automatically: analyze commits, draft notes, bump version, push to develop, fast-forward merge to main, tag and create the GitHub release, switch back to develop, prepare the next cycle, and push.
Step 0: Validate arguments
Both $version and $next_version must be present and match X.Y.Z or X.Y.Z-prerelease (e.g. 6.3.0, 6.3.0-beta.1, 6.4.0-dev). If either is missing or malformed, stop and ask the user for the correct value.
Step 1: Validate preconditions
- Run
git branch --show-current— must be ondevelop. - Run
git status --porcelain— working tree must be clean. If dirty, stop and tell the user to commit or stash. - Run
node scripts/release.ts since-last— note the last released tag.
Step 2: Analyze commits
Run git log <last-tag>..HEAD --format="%h %s" to get all commits since the last release.
If there are zero commits, tell the user there's nothing to release and stop.
Step 3: Study the release notes style
Run gh release view <last-tag> to read the most recent release notes body. This is your primary style reference.
Also read the second-most-recent release for additional context: run gh release view <tag-before-that>.
Internalize these style rules:
- Title:
## Kobato X.Y.Z(h2, with "Kobato" prefix) - Lead paragraph: 1–2 sentences summarizing the release themes, with bolded feature names inline
- Sections: Use
###headers with emoji prefixes —### ✨ New Features,### 🛡️ Security Hardening,### 🏗️ Architecture & Refactoring,### 🔧 Build & Dependencies,### 🐛 Fixes. Only include sections that have entries. Add extra sections (e.g.,### 🎨 UI Redesign,### 🎵 Music Player) if a thematic grouping makes sense. - Sub-headers:
**Bold Title Case**to group related items within a section. - Bullets: Each change is a single
-bullet, concise and technical. Describe what changed and often why. Use sentence case. - Language: English. Technical, precise, no first person.
- Emojis: Only as section header prefixes, never inline.
- Footer:
**Full Changelog**: [prev...current](https://github.com/syhily/kobato/compare/PREV...CURRENT)— a clickable markdown link
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.
- 2mo ago First seen · 94 lines · 46 tokens per session scan A cb2e9dff4fc5
release is a skill published in the GitHub repository syhily/kobato (114 stars, last pushed 7d ago), licensed MIT. It adds 46 tokens to every session and 1,150 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-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.
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.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.