Borrowing it
Nothing to install: this file belongs to mpolatcan/codehub. 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/mpolatcan/codehub/main/.claude/skills/release-cut/SKILL.mdgit clone --depth 1 https://github.com/mpolatcan/codehubWrote 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/mpolatcan/codehub/release-cut)<a href="https://agentmods.dev/skills/mpolatcan/codehub/release-cut"><img src="https://agentmods.dev/badge/skills/mpolatcan/codehub/release-cut/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/mpolatcan/codehub/release-cut"><img src="https://agentmods.dev/badge/skills/mpolatcan/codehub/release-cut.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.00054 | $0.00888 |
| Opus 5.5 | $0.00022 | $0.00355 |
| Sonnet 5.5 | $0.00011 | $0.00178 |
| Haiku 4.5 | $0.00005 | $0.00089 |
Grade A, and why
release-cut 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut a CodeHub release
Pre-flight required:
- Working tree clean on
main TEST_SCENARIOS.mdregression checklist (the end-of-doc list) has been walked manuallycargo checkclean insidesrc-tauri/npm run buildclean- Docker Hub credentials available for
ghcr.io/mpolatcan/codehub-runtime
1. Bump version everywhere
The version appears in four places. Update all to the same value (X.Y.Z):
package.json—"version": "X.Y.Z"src-tauri/Cargo.toml—version = "X.Y.Z"under[package]src-tauri/tauri.conf.json—"version": "X.Y.Z"src-tauri/src/lib.rs—const DEFAULT_IMAGE: &str = "ghcr.io/mpolatcan/codehub-runtime:X.Y.Z";
Commit the version bump as its own commit: chore: bump version to X.Y.Z.
2. Publish the runtime image
From repo root, after the version bump in step 1 is committed:
make image-push # multi-arch buildx push (linux/amd64, linux/arm64)
The image-push target reads the tag from src-tauri/src/lib.rs:DEFAULT_IMAGE and also retags :latest.
Verify the manifest after push:
docker buildx imagetools inspect ghcr.io/mpolatcan/codehub-runtime:X.Y.Z
Both linux/amd64 and linux/arm64 platforms must be listed.
3. Build the desktop bundles
make build
Outputs land in src-tauri/target/release/bundle/:
- macOS:
dmg/CodeHub_X.Y.Z_aarch64.dmgand/or_x64.dmg - Linux:
deb/codehub_X.Y.Z_amd64.deb,appimage/codehub_X.Y.Z_amd64.AppImage
On macOS, repeat the build inside an x86_64 host (or use --target x86_64-apple-darwin) if you want a universal release. Sign + notarize with xcrun notarytool before publishing if you have a developer ID.
4. Tag + push
git tag -a vX.Y.Z -m "CodeHub X.Y.Z"
git push origin vX.Y.Z
5. GitHub release
gh release create vX.Y.Z \
--title "CodeHub X.Y.Z" \
--notes-file CHANGELOG-NEXT.md \
src-tauri/target/release/bundle/dmg/*.dmg \
src-tauri/target/release/bundle/appimage/*.AppImage \
src-tauri/target/release/bundle/deb/*.deb
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 · 97 lines · 54 tokens per session scan A c1c40f691c32
release-cut is a skill published in the GitHub repository mpolatcan/codehub (6 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 888 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-tag
Cut a release tag behind a real tier gate and cloud approval readback. The approval, task, approved commit, and resulting tag are bound; self-approval and HEAD drift fail closed. Prod prefixes remain refused.
git-ops
Close out a local coding task on the bound daemon — stage, commit, branch, merge, push via cloud git — and when a merge conflicts, STOP and escalate with the file list instead of auto-resolving. Push reaches only the bare replica; prod-triggering tags are refused.
release-rollback
Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and (with --mirror) repoints the bare mirror ref. Behind an approval gate; with no previous good version it BLOCKS instead of…
releasing-prod
A controlled process for deploying already tested changes to the production environment. Production is the live environment used by users, and this process includes owner approval, database migration checks, deployment, and smoke tests.
create-release
Create a versioned GitHub release with changelog.
release
Release a validated Open Harness commit by pushing it to main or master, then monitor the automatic SemVer/GHCR/GitHub Release workflow. TRIGGER when: asked to release, version, ship, cut a release, or verify release artifacts.