Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/frostney/gocciascript/prepare-releasenpx skills add frostney/GocciaScript --skill prepare-releasegit 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.svg" alt="Measured on agentmods" 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 | $0.00096 | $0.02194 |
| Opus 5 | $0.00048 | $0.01097 |
| Sonnet 5 | $0.00019 | $0.00439 |
| Haiku 4.5 | $0.00010 | $0.00219 |
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 4d 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 a draft prep PR via
/create-pr— the final review gate.
Hard blockers — stop and report
- The
DEFINITION_OF_DONEgate is red (build,tests,tests --mode=bytecode, 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
git fetch origin; confirm the branch is a fresh branch off the default branch and the tree is clean. Stop if not.- 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.
- 4d 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,194 once invoked, about $0.0005 per session on Opus 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
qcad
Use when editing DXF files with a professional open-source 2D CAD application — CAM output, part libraries, isometric projection. QCAD: open-source 2D CAD with DXF as native format, scriptable via ECMAScript.
oxc-docs
Comprehensive reference for the JavaScript Oxidation Compiler (Oxc) — a collection of high-performance JavaScript tools written in Rust. Covers parser design (lexer, AST, parser, errors, semantic analysis), architecture (parser, linter, test infrastructure, AST tools), ECMAScript specification and grammar, performance…
git-step-commit
Analyze Git changes, split them into coherent commits, infer message language and format, optionally close supplied GitHub issues, and execute safely. Manage persistent global or repository preferences for review versus direct submission and automatic or specified commit-message language through native Git config.…
manage-prd-docs
Automatically manage product requirements across current decisions in docs/PRD.md and docs/prd/, mature future plans under docs/plans/, and active implementation under docs/work/. Use whenever the conversation discusses, clarifies, versions, plans, implements, completes, splits, or migrates a product requirement or…
modernize-ecmascript
当 Agent 编写或修改 JavaScript、TypeScript，用户要求按指定环境、输出版本、ES20xx 或具体语法编写代码，询问某项 ECMAScript 语法、标准内置 API 或提案能否采用，或者要求审查仓库中可简化、可现代化的写法时，应使用本 Skill。围绕目标文件真实经过的解析器、转换器和输出目标判断新语法能否安全采用，并按需读取 TC39 Atlas 的提案阶段、官方仓库、polyfill 与实现线索。.
codebase-audit
Audits the current repository for systemic correctness, architecture, churn, simplification, clarity, test value, and operational risks using current source and reproducible probes. It can delegate evidence gathering across bounded capability and perspective lanes. Use when the user runs /codebase-audit or asks for an…