Borrowing it
Nothing to install: this file belongs to jonathanung/strike. 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/jonathanung/strike/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/jonathanung/strikeWrote 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/jonathanung/strike/release)<a href="https://agentmods.dev/skills/jonathanung/strike/release"><img src="https://agentmods.dev/badge/skills/jonathanung/strike/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/jonathanung/strike/release"><img src="https://agentmods.dev/badge/skills/jonathanung/strike/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.00045 | $0.01411 |
| Opus 5.5 | $0.00018 | $0.00564 |
| Sonnet 5.5 | $0.00009 | $0.00282 |
| Haiku 4.5 | $0.00005 | $0.00141 |
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 today.
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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release (strike-cli)
Ship a version tag that triggers .github/workflows/release.yml (multi-arch CLI archives + GitHub Release). Pre-release tags also attach unsigned desktop installers.
Preconditions
gh auth statusok; push rights to the repo that owns tags.- Working tree clean on an up-to-date
main(or explicit commit SHA to tag). - User confirmed version number (e.g.
v0.1.0) and that this is intentional.
Stop-and-ask if main CI is red, an open release-block issue exists, or the tag already exists.
Preflight
git fetch origin main --tags
git checkout main
git merge --ff-only origin/main
git status -sb # must be clean, main == origin/main
gh run list --branch main --limit 3 # latest CI success preferred
git tag -l 'v*' | tail -5
git log "$(git describe --tags --abbrev=0)..HEAD" --oneline
Load test-and-validate tier B (or C if trust-boundary commits dominate since last tag). Prefer green CI on main over re-running the full suite locally when CI is already success on HEAD.
Optional: load smoke for a quick product check.
Changelog
Draft the version entry from git log PREV..HEAD before tagging. Follow the
standard in CHANGELOG.md and docs/contributing.md: rename [Unreleased] to
[vX.Y.Z] - YYYY-MM-DD, add a fresh [Unreleased], and update the comparison
links. Commit and push that entry to main; the release workflow fails if the
tag has no matching non-empty entry.
Include:
- User-facing changes grouped under the standard categories
- Breaking/default changes (keybinds, config) if any
- Upgrade note when relevant
Do not ship install-only boilerplate or copy implementation-only commit activity into the changelog.
Tag and push
VERSION=v0.x.y # user-confirmed
git tag -a "$VERSION" -m "strike $VERSION
<one-line summary>
"
git push origin "$VERSION"
Never force-push tags. Never tag a dirty tree or a commit not on origin/main unless the user explicitly requests a pre-release from a branch.
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.
- today Changed · +42 lines 73660e3cbb27
- 2mo ago First seen · 103 lines · 45 tokens per session scan A a569a6bf770d
release is a skill published in the GitHub repository jonathanung/strike (5 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 1,411 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
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.