A release checklist and procedure for publishing PwrSnap, a desktop application, in versions such as alpha, beta, release candidate, or stable.

Use it to prepare release metadata, create tags, publish desktop releases, and monitor the release process.

It reduces mistakes by checking the correct version file, Git tag, changelog, branch, and release workflow before publishing.

How pwrdrvr/PwrSnap configures Codex

Reuse

Borrowing it

Nothing to install: this file belongs to pwrdrvr/PwrSnap. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/pwrdrvr/PwrSnap/main/.agents/skills/release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/pwrdrvr/PwrSnap

Made for: 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/pwrdrvr/pwrsnap/release.svg)](https://agentmods.dev/skills/pwrdrvr/pwrsnap/release)

Your own site

<a href="https://agentmods.dev/skills/pwrdrvr/pwrsnap/release"><img src="https://agentmods.dev/badge/skills/pwrdrvr/pwrsnap/release.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 3,530 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 pass 7 Sept 2026

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.00097	$0.03530
Opus 5	$0.00048	$0.01765
Sonnet 5	$0.00019	$0.00706
Haiku 4.5	$0.00010	$0.00353

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

Security

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

.agents/skills/release/SKILL.md · 369 lines

How it starts

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

Release

Use this skill for PwrSnap desktop releases published by .github/workflows/release.yml.

Read First

Read these files before changing release metadata:

Guardrails

Release from main for the active next-version train, or from a long-lived maintenance branch named releases/<major>.<minor> for a stable promotion explicitly requested from an accepted prerelease or for patch releases on a prior train. Do not include the patch component in maintenance branch names: use releases/1.0, not releases/1.0.x or releases/1.0.1.
Start from a clean working tree. If tracked files are dirty, stop and ask before changing release metadata.
Fetch tags before planning:
```
git fetch origin --tags
```
Treat apps/desktop/package.json as the desktop release version source. The root package.json version is not the desktop app release version.
Always use a leading-v tag such as v0.0.1-alpha.5.
The tag version, apps/desktop/package.json version, and CHANGELOG.md release heading must match.
Before moving main to a new major/minor train, verify that the prior train's maintenance branch exists. For example, before preparing 1.1.0-beta.1 from a current 1.0.* main, check for origin/releases/1.0. If it is missing, stop and ask whether to create it from the current prior-train release commit before bumping version metadata.
Patch releases for an existing train must land on that train's branch. For example, prepare v1.0.1 on releases/1.0, not on main.
Do not create or push the tag until the version and changelog are committed and present on the intended release branch.
Before pushing a release tag, verify the apple-signing GitHub Environment exists on pwrdrvr/PwrSnap, requires reviewer approval, is scoped to v* release tags, and has the Apple signing/notarization secrets required by the workflow. Apple signing/notarization secrets must NOT exist as repository-level secrets.
Do not use GitHub generated release notes as the final notes.
Do not create the GitHub Release by hand before the build succeeds. Let the CI publish job create it from the signed/notarized build and matching changelog notes.
Do not force-push the default branch or rewrite an existing release tag without explicit user approval.
Keep the MIT license intact: do not swap LICENSE for a different SPDX or drift any workspace package.json away from "license": "MIT".

Read the full file on GitHub · 369 lines

Files

What ships with it

1 file 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.

agents/openai.yaml 171 B

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.

8d ago First seen · 369 lines · 97 tokens per session scan A 4545d6770d68

Subscribe to this mod's changes

release is a skill published in the GitHub repository pwrdrvr/PwrSnap (5 stars, last pushed yesterday), licensed MIT. It adds 97 tokens to every session and 3,530 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-31.

Git and workflow Releases acp ai-tools codex grok-build screen-capture screenshot

omh-deploy-and-monitor

This is a Hermes-native deploy-and-monitor workflow skill.

rlaope/oh-my-hermes · 66 tokens

git-wrapup

Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…

cyanheads/obsidian-mcp-server · 82 tokens

release-and-publish

Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…

cyanheads/obsidian-mcp-server · 112 tokens

release-notes

Draft user-facing release notes from a git log range. Trigger when the user asks for "release notes", "changelog entry", or "what shipped this week" with a git ref range. Output is markdown sections grouped by Features / Fixes / Breaking with PR links.

jnMetaCode/ai-coding-guide · 59 tokens

finalize

Finalize orphaned recordings - stop processes, compress, push to orphan branch. TRIGGERS - finalize recording, stop asciinema, orphaned recording.

terrylica/cc-skills · 33 tokens

github

Use when automating GitHub issues, pull requests, reviews, CI checks, labels, releases, or engineering collaboration loops through the GitHub CLI.

seaworld008/Commonly-used-high-value-skills · 32 tokens

PwrSnap: Skill for Codex