Borrowing it
Nothing to install: this file belongs to eyalBPM/SessionDeck. 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/eyalBPM/SessionDeck/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/eyalBPM/SessionDeckWrote 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/eyalbpm/sessiondeck/release)<a href="https://agentmods.dev/skills/eyalbpm/sessiondeck/release"><img src="https://agentmods.dev/badge/skills/eyalbpm/sessiondeck/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/eyalbpm/sessiondeck/release"><img src="https://agentmods.dev/badge/skills/eyalbpm/sessiondeck/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.00060 | $0.01369 |
| Opus 5.5 | $0.00024 | $0.00548 |
| Sonnet 5.5 | $0.00012 | $0.00274 |
| Haiku 4.5 | $0.00006 | $0.00137 |
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 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releasing SessionDeck
release.ps1 takes committed code to a published GitHub release in one command. The
<Version> in SessionDeck.csproj is the single source of truth — the script derives
the tag, the zip name and the release title from it.
.\release.ps1 -DryRun # everything except the sync-commit and the actual release
.\release.ps1 # the real thing
Always do a -DryRun first. It exercises every guard, the publish, the tests and the
packaging, so a failure surfaces before anything is pushed.
The release policy
Exactly one release on GitHub — always the current version. Releases here are frequent, and every one carries a self-contained ~58MB zip; keeping them would pile up downloads nobody wants. So every existing release is deleted on each run, whatever its version line.
Three things used to die together. Only one of them was clutter, so now they part ways:
| Kept? | Why | |
|---|---|---|
| The zip of an old version | deleted | This is the clutter. Rebuildable in minutes. |
| Its tag | kept | The only way back to an exact past build, and invisible on the Releases page. Rollback = git checkout v0.9.4 + publish. |
| Its notes | kept, in CHANGELOG.md |
A page that gets deleted cannot hold history. |
Consequences worth knowing:
- The notes baseline is the newest tag below the version being released, not the newest release. Under the old release-derived baseline every replacement destroyed its own baseline, so the notes shrank on each patch (v0.9.4 said "since v0.9.3" with 5 commits; v0.9.5 said "since v0.9.4" with 2, and everything before it was gone).
release.ps1prepends the new section toCHANGELOG.mdand commits it before the push, so the tagghcreates already points at a commit that documents itself. The file needs its<!-- new releases are inserted directly below this line -->marker — the script blocks if it's missing.- The release is always
--latest. There is no version-line arithmetic left. - A downloadable zip exists only for the current version. If someone needs an older build, check out its tag and publish.
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 · 106 lines · 60 tokens per session scan A cb7539abd204
release is a skill published in the GitHub repository eyalBPM/SessionDeck (1 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 1,369 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
changelog-rewriter
Rewrites changelog entries with cheeky, narrative flair following project conventions. Use this when asked to rewrite or update CHANGELOG.md entries.
release-notes
A release-automation tool that uses Conventional Commits, a standard commit-message format, to prepare a software release.
shipping-and-launch
A pre-launch checklist and rollout guide for releasing software safely. It covers quality checks, monitoring, staged releases, and plans for reversing a release if something goes wrong.
release
Automated release management - version updates, changelog generation, git tagging, and GitHub release creation.
release
Release preparation workflow - security audit → E2E tests → review → changelog → docs.
changesets
Concise PR finalization changesets. Use when implementation scope is complete and focused validation has finished to classify release impact, consolidate the PR's existing changeset, or write its consumer release note.