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/prepare-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/prepare-release)<a href="https://agentmods.dev/skills/frostney/gocciascript/prepare-release"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/prepare-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/prepare-release"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/prepare-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.00096 | $0.02277 |
| Opus 5.5 | $0.00038 | $0.00911 |
| Sonnet 5.5 | $0.00019 | $0.00455 |
| Haiku 4.5 | $0.00010 | $0.00228 |
Grade A, and why
prepare-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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare Release
Project-specific pre-flight that gets the GocciaScript repository into a releasable, truthful, verified state and hands off to /create-release. The deliverable is a prep PR (via /create-pr) plus a readiness report.
This skill stops before /create-release begins. Reuse the gates in DEFINITION_OF_DONE.md rather than restating them, and defer the general engineering bar to software-engineering-excellence.
Boundary
- In scope: verification, source-truth sync (docs, website,
CONTEXT.md, README), changelog categorization preview, conformance and generated-data checks, housekeeping, and opening the prep PR. - Out of scope (owned by
/create-release): computing the next version, writing the changelog section, therelease/<version>branch, the tag, and publishing. CI owns the tag-triggered publish — seedocs/build-system.md§ CI Integration.
Flow
Read-only first, one approval checkpoint, then apply, then hand off:
- Run every non-mutating check (verify, conformance read, currency sweep, generated-data verify).
- Present one consolidated readiness report (see below).
- Stop for the user to approve or veto per category (e.g. "skip the website this cycle").
- Apply approved fixes (each category's diff visible), then re-run the verify gate.
- Open the prep PR via
/create-pr— the final review gate.
Hard blockers — stop and report
- The
DEFINITION_OF_DONEgate is red (build,tests, orformat --checkfails). - The working tree is dirty/unexpected, or the branch is behind the base (per
git-workflow).
Deliberate non-blocker
- A test262 conformance regression reports loudly but never blocks — it is non-blocking in CI by design, and is a judgment call for the user, not a gate.
Steps
1. Preflight
- Apply
git-workflow's clean-worktree and fresh-base preflight; stop if it fails. - After a merge, branch switch, or generated-resource change, build clean to rule out stale FPC artifacts before trusting any failure:
./build.pas --clean <target>(seedocs/contributing/tooling.md§ Stale FPC Build Artifacts).
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 Changed · -1 lines 76adf409a2ad
- 25d ago Changed · +1 lines 97aaf7aa3525
- 26d ago Changed 3af1a9bbeeef
- 1mo ago First seen · 112 lines · 96 tokens per session scan A 2c1415c1f9b8
prepare-release is a skill published in the GitHub repository frostney/GocciaScript (20 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 2,277 once invoked, about $0.0004 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…