Borrowing it
Nothing to install: this file belongs to frostney/GocciaScript. 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/frostney/GocciaScript/main/.agents/skills/create-release/SKILL.mdgit clone --depth 1 https://github.com/frostney/GocciaScriptWrote 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/frostney/gocciascript/create-release)<a href="https://agentmods.dev/skills/frostney/gocciascript/create-release"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/create-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/frostney/gocciascript/create-release"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/create-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.00930 |
| Opus 5.5 | $0.00020 | $0.00372 |
| Sonnet 5.5 | $0.00010 | $0.00186 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
create-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 22d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- create-release — 88% identical, 53 lines differ
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create release
Prepare a release whose tag contains its changelog, then publish through exactly one evidence-backed path when publication is authorized.
Authorization
- Prepare: determine the version, update changelog/version declarations, validate, and open the release PR. Requests to prepare, bump, or generate notes authorize only this stage.
- Publish: after the PR merges, create or trigger the tag/release through the
repository's established publisher. Requests to cut, tag, publish, or run
/create-releaseauthorize this stage too. - A
/milestone-rushcaller supplies publication authority at its verified milestone boundary. Reuse its settled release plan and version; no separate user command is required./deliverintegration delivery is not this trigger. - When standalone authorization is ambiguous, perform Prepare only.
Invariants
- The changelog and version bump land before the tag, through a squash-merged PR.
- Use the repository's configured tools and current documentation. Regenerate generated changelogs rather than hand-editing them.
- Run the declared release-relevant gate and report only observed results.
- Never amend, force-push, force-update a tag, skip hooks, or publish through more than one path.
Prepare
- Require a clean working tree, then resolve the authorized stage, remote default branch, changelog/version tooling, last release, remote tags, workflows, and release documentation.
- Stop if there are no releasable commits.
- Use a settled explicit version, or compute it under the project's deterministic version policy. When neither settles it, recommend a version from the unreleased conventional commits and ask for that choice.
- Create a release branch from the fresh remote base.
- Generate the changelog section and update every authoritative version declaration using project tooling. Do not invent a manifest bump when the project derives its version from tags.
- Run the release-relevant gate, commit
chore(release): <version>, and open a draft release PR through/create-prwith the changelog section and observed validation. Prepare-only requests end here.
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.
- 22d ago Changed · +3 lines b0890c427e4e
- 26d ago Changed · +22 tokens per session c815b805072b
- 29d ago Changed · +4 lines · -25 tokens per session d63ec6c3bd65
- 1mo ago First seen · 81 lines · 54 tokens per session scan A 273c29240f92
create-release is a skill published in the GitHub repository frostney/GocciaScript (20 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 930 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-30.
Other skills, from other repositories
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
playground-snapshot-release
Publish a Playground UI snapshot (@mastra/playground-ui and its workspace dependencies) from main or the current branch via the playground-snapshot mode of the Publish to npm workflow, wait for it to finish, then open a PR on mastra-ai/platform bumping the frontend to the published snapshot version. Use when asked to…
pr-snapshot-release
Guide a Mastra maintainer through publishing an npm snapshot from a pull request or a specified repository branch. Use when asked to release, publish, or create a PR snapshot, branch snapshot, canary package build, or branch-specific npm tag. Performs source and branch preflight checks, requires confirmation before…
publish-release
Cut and publish a versioned release of @loopdive/js2 + the js2wasm proxy — bump both manifests in lockstep, land a reviewed release PR, then push the vX.Y.Z tag that triggers npm/JSR publish. Use this whenever the user wants to release, publish, ship, cut, or tag a version, bump the version number, push a release tag…
multipublish
Publish monorepo packages simultaneously to npm and JSR via a platforms config array. Integrates with changesets via stdin pipe or --useChangesetStatus flag. Use experimentalGenerateJSR to skip maintaining a jsr.json. Supports pnpm, bun, npm, yarn (jsr and npm); deno (jsr only). Config via cosmiconfig or package.json…