A release procedure for the pi-agent-dashboard project. It updates the changelog and package versions, creates a Git tag, and pushes it so the project's release workflow can publish packages and build desktop files.

Use it to cut a production or pre-release version of pi-agent-dashboard and trigger its package, desktop-artifact, and GitHub Release process.

It turns the project's release steps into a checked sequence with requirements such as a clean branch, passing tests, and a successful build. This reduces the chance of publishing from the wrong state.

release-cut — Skill for Claude Code and Codex by BlackBeltTechnology

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard

agentmods

npx agentmods add skills/blackbelttechnology/pi-agent-dashboard/release-cut

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/release-cut/github.svg)](https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/release-cut)

Your own site

<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/release-cut"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/release-cut"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/release-cut.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,577 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Agent Snooping · line 248
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.

Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00093	$0.04577
Opus 5	$0.00046	$0.02289
Sonnet 5	$0.00019	$0.00915
Haiku 4.5	$0.00009	$0.00458

Measured 10d ago against content hash ce2207a4bb91, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 10d 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.

.pi/skills/release-cut/SKILL.md · 330 lines

How it starts

The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cut a pi-agent-dashboard Release

Canonical reference: docs/release-process.md. This skill automates steps 1–5 of that doc. Production tags (vX.Y.Z) publish the GitHub Release automatically — electron-updater's default GitHub provider only resolves published, non-draft releases, so a draft would silently block auto-update. Pre-release tags (vX.Y.Z-rc.N) stay drafts so a maintainer can eyeball artifacts before flipping to published. See change: fix-electron-auto-update-pipeline.

Pre-flight (MUST pass before touching anything)

Run these in order. If any fails, stop and report — do not continue.

Clean working tree
```
git status --porcelain
```
Must be empty. If not, ask the user to commit or stash.
On the release branch
```
git rev-parse --abbrev-ref HEAD
```
Must be develop (this repo has no main). If elsewhere, ask user to confirm before continuing.
Up to date with origin
```
git fetch origin && git status -sb
```
Branch must NOT be "behind". If behind, ask user to pull first.
Tests pass
```
pnpm test
```
Build succeeds
```
pnpm run build
```
Dependency-shape gate (introduced by enable-standalone-npm-install to prevent regressions of v0.5.3 publish-time bugs)
```
node scripts/verify-release-deps.mjs
```
Asserts critical runtime deps (jiti, pinned node-pty, etc.) are still declared in the publishable workspace package.json files. Failure means the next published tarball would be broken — STOP and fix the workspace before cutting.

Known false-positive (substring gate). verify-release-deps.mjs checks the declared range with a naive String.includes(minVersion) — NOT semver math. So a legitimate pi bump ABOVE the floor (e.g. floor 0.74.0, pin ^0.80.10) fails the gate because "^0.80.10" does not contain the substring "0.74.0". When this fires and the pin is genuinely newer than the rule's minVersion, the FIX is to bump that rule's minVersion (+ its evidence note in the RULES array, and the scripts/AGENTS.md row) to the new floor — do NOT downgrade the pin. This recurs on every pi version bump. See change: fix-release-lockfile-drift (gate lives in scripts/verify-release-deps.mjs).

Read the full file on GitHub · 330 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

10d ago First seen · 330 lines · 93 tokens per session scan A ce2207a4bb91

Subscribe to this mod's changes

release-cut is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (278 stars, last pushed yesterday), licensed MIT. It adds 93 tokens to every session and 4,577 once invoked, about $0.0005 per session on Opus 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.

Git and workflow Releases agent agent-framework agent-orchestration agent-skills agentic agentic-ai

akiship

Full release ritual end-to-end — front-loaded checks, then an unattended pass. ACTIVATION IS LITERAL: this skill runs only on a user turn containing the exact token /akiship that asks for the run to be performed. Nothing else activates it — not the bare word "akiship", not a release-flavored paraphrase, and never a…

lacvietanh/akidevrule · 0 tokens

public-plugin-packaging

Use when packaging an Agentlas agent repo for public GitHub release, Codex plugin submission, Claude adapter distribution, or one-line terminal installation.

agentlas-ai/Agentlas-OS · 34 tokens

akigitcommit

Analyze the working tree and commit changes in clean logical groups. Triages a long half-finished tree first (finished vs mid-edit vs abandoned vs accidental) before grouping. Auto-detects CHANGELOG to switch between domain-grouped mode (3–5 commits by object/feature) and type-grouped mode (feat/fix/refactor). Stages…

lacvietanh/akidevrule · 100 tokens

release-cut