Borrowing it
Nothing to install: this file belongs to luthersystems/elps. 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/luthersystems/elps/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/luthersystems/elpsWrote 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/luthersystems/elps/release)<a href="https://agentmods.dev/skills/luthersystems/elps/release"><img src="https://agentmods.dev/badge/skills/luthersystems/elps/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/luthersystems/elps/release"><img src="https://agentmods.dev/badge/skills/luthersystems/elps/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.00000 | $0.01507 |
| Opus 5.5 | $0.00000 | $0.00603 |
| Sonnet 5.5 | $0.00000 | $0.00301 |
| Haiku 4.5 | $0.00000 | $0.00151 |
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 today.
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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release — Create a GitHub Release
Cuts a tagged release by dispatching the repository's release pipeline,
.github/workflows/release-tag.yml. The pipeline validates the version,
generates release notes from the commits since the last stable tag, and
creates the tag + GitHub Release with the official Claude App token; the
tag-push event then triggers vscode-publish.yml (platform elps binaries +
VS Code Marketplace extension).
Use the pipeline. Do not create the tag or release by hand. Two reasons, both documented in the workflow's own header:
- A tag created with the default
GITHUB_TOKEN(e.g.gh release createfrom a workflow, or an Actions-context push) does NOT triggervscode-publish.yml— GitHub suppresses workflow→workflow events for that token. The release would exist but the binaries and extension would never publish. - Direct tag pushes are blocked from agent sandboxes, so
git push origin vX.Y.Zis not available there anyway.
A release is externally visible immediately — the tag publishes the VS Code extension to the Marketplace. Treat cutting one as a production action.
Trigger
Use when asked to create a release, tag a release, cut a release, or ship a version.
Arguments
Optional: version bump type or explicit version.
patch(default) — bump patch: v1.44.0 -> v1.44.1minor— bump minor: v1.44.0 -> v1.45.0major— bump major: v1.44.0 -> v2.0.0vX.Y.Z— explicit version
Workflow
1. Determine the version
git fetch --tags origin
LATEST=$(git tag --list 'v*' | grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' | sort -V | tail -1)
echo "Latest stable tag: $LATEST"
git log $LATEST..origin/main --oneline
If there are no unreleased commits, stop and say so. Compute the next
version from the bump argument (or use the explicit version). The pipeline
re-validates — exact vMAJOR.MINOR.PATCH format with no leading zeros,
strictly newer than the latest stable tag by semver — and refuses anything
else, so a wrong guess fails safely rather than shipping.
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.
- today Changed · +2 lines 83284a36ce43
- 2d ago First seen · 142 lines · 0 tokens per session scan A e94df37d13b4
release is a skill published in the GitHub repository luthersystems/elps (36 stars, last pushed today), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 1,507 tokens. 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-10-26.
Other skills, from other repositories
release
Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
crawlkit
Maintain and release the crawlkit Go library, preserving downstream compatibility for gitcrawl, slacrawl, discrawl, and notcrawl.
tools-checkout
Fetch the internal tools repository at a pinned release.
pi-sync
Daily upstream-sync job for the pi Go port — fetch upstream pi, triage every change since the recorded pin, port what's in scope, verify idiomatic + parity via independent reviews, update the ledger, and push. Use for "sync with upstream", "porting job", or as the scheduled daily run.