Borrowing it
Nothing to install: this file belongs to a9a4k/vscode-deck. 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/a9a4k/vscode-deck/main/.agents/skills/release/SKILL.mdgit clone --depth 1 https://github.com/a9a4k/vscode-deckWrote 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/a9a4k/vscode-deck/release)<a href="https://agentmods.dev/skills/a9a4k/vscode-deck/release"><img src="https://agentmods.dev/badge/skills/a9a4k/vscode-deck/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/a9a4k/vscode-deck/release"><img src="https://agentmods.dev/badge/skills/a9a4k/vscode-deck/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.00082 | $0.00855 |
| Opus 5.5 | $0.00033 | $0.00342 |
| Sonnet 5.5 | $0.00016 | $0.00171 |
| Haiku 4.5 | $0.00008 | $0.00085 |
Grade C, and why
release scanned grade C with 1 finding 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 1mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Note: `npm version` may strip linux-only optional peer entries from `package-lock.json` on darwin. That's the accepted status quo — sandcastle's next merger detects the drift and auto-commits `fix: synchronize npm lockfi How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Cut a new release of the vscode-deck extension.
Preconditions to check first (fail loudly if any miss):
- Working tree is clean (
git status --shortprints nothing). - On
mainbranch. npm testpasses.
Steps
-
Read current version and pick target. Read
package.jsonfor the current version. Ask the user for the explicit targetX.Y.Z(this skill does not compute bumps — you pick the exact version). Show recent releases for context:git log --oneline --grep='chore(release)' -5 -
Ask for the summary line. The commit title format is:
chore(release): X.Y.Z — <summary>Summary is one line, often ends with issue refs like
(#151, #152, #153). Look at recent releases for tone. If the release has more nuance than one line can hold, ask if they want a longer commit body — otherwise the message is just the title +Co-Authored-Bytrailer. -
Write the changelog entry. Add a user-facing
## X.Y.Zentry toCHANGELOG.md, directly below the title so entries remain newest-first. Summarize what changed as readable release notes rather than copying commit messages. -
Bump.
npm version <target> --no-git-tag-versionUpdates
package.jsonandpackage-lock.jsonversion fields. Does not create a tag (we make one manually in step 5 so the commit format stays clean).Note:
npm versionmay strip linux-only optional peer entries frompackage-lock.jsonon darwin. That's the accepted status quo — sandcastle's next merger detects the drift and auto-commitsfix: synchronize npm lockfile. Don't try to regen the lockfile here (a freshrm -rf node_modules && npm installcan pull newer transitive deps, drifting the release from what was tested). -
Commit. Use a HEREDOC to preserve formatting:
git add CHANGELOG.md package.json package-lock.json git commit -m "$(cat <<'EOF' chore(release): X.Y.Z — <summary> Co-Authored-By: <your model attribution> <[email protected]> EOF )"Attribution: use the current session's model name (e.g.
Claude Opus 4.7,Claude Fable 5). Do not hardcode.
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.
- 1mo ago Changed · +5 lines 3ab329281931
- 2mo ago First seen · 74 lines · 82 tokens per session scan C 3f87d4cec841
release is a skill published in the GitHub repository a9a4k/vscode-deck (14 stars, last pushed 16d ago), licensed MIT. It adds 82 tokens to every session and 855 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). 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-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.