Borrowing it
Nothing to install: this file belongs to jenreh/appkit. 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/jenreh/appkit/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/jenreh/appkitWrote 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/jenreh/appkit/release)<a href="https://agentmods.dev/skills/jenreh/appkit/release"><img src="https://agentmods.dev/badge/skills/jenreh/appkit/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/jenreh/appkit/release"><img src="https://agentmods.dev/badge/skills/jenreh/appkit/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.00037 | $0.00325 |
| Opus 5.5 | $0.00015 | $0.00130 |
| Sonnet 5.5 | $0.00007 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00032 |
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 1mo 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
Ask the user which version bump to apply, then run task release:build.
Step 1 — ask
Use AskUserQuestion to ask:
Question: "Which version component should be bumped?" Header: "Version bump" Options:
patch— backwards-compatible bug fixes and minor improvements (Recommended)minor— new backwards-compatible featuresmajor— breaking changes
Step 2 — confirm current version
grep '^version = ' pyproject.toml | cut -d '"' -f2
Show the user: "Current version is X.Y.Z — bumping [choice] will release X.Y.Z+1. Proceed?"
If they say no, stop.
Step 3 — run the release
task release:build -- <choice>
Stream the output so the user can see progress. The task will:
- Bump the version in all tracked files
- Commit and push
- Generate an AI-written changelog from commits since the last tag
- Create a GitHub release with that changelog
Step 4 — report
After the task completes, show the new version and the GitHub release URL from the output.
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.
- 1mo ago First seen · 48 lines · 37 tokens per session scan A 688cc9f54a7d
release is a skill published in the GitHub repository jenreh/appkit (4 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 325 once invoked, about $0.0001 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
project-graveyard
Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions…
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
cli-release
Release and recover first-party Composio CLI binaries through Build CLI Binaries, including automatic beta builds, promote-stable dispatches, beta-tag selection, asset and installation verification, and failed release recovery. Use when a contributor asks to build a CLI beta, publish or promote a stable CLI version…
config-loading-precedence
How Xberg resolves configuration — CLI-mode and server/MCP-mode precedence orders, project config walk-up, user config fallback, field-level inline JSON merge (mergejsonintoconfig), the ExtractionOverrides CLI layer, and the two mechanisms that make a config change silently do nothing. Load when adding a config flag…
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
release-versioning
How xberg versions are synced and released — Cargo.toml is the single source of truth, task version:sync propagates it to alef-managed binding manifests AND the integrations under integrations/, which are versioned and published in lockstep with core (including -rc.N). Load before bumping a version, editing the…