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 skills add starcat-app/Starcat --skill starcat-release-readinessgit clone --depth 1 https://github.com/starcat-app/StarcatWrote 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/starcat-app/starcat/starcat-release-readiness)<a href="https://agentmods.dev/skills/starcat-app/starcat/starcat-release-readiness"><img src="https://agentmods.dev/badge/skills/starcat-app/starcat/starcat-release-readiness/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/starcat-app/starcat/starcat-release-readiness"><img src="https://agentmods.dev/badge/skills/starcat-app/starcat/starcat-release-readiness.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.00113 | $0.01379 |
| Opus 5.5 | $0.00045 | $0.00552 |
| Sonnet 5.5 | $0.00023 | $0.00276 |
| Haiku 4.5 | $0.00011 | $0.00138 |
Grade A, and why
starcat-release-readiness 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 5d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Starcat 发版准备
以可验证证据把目标版本从 dev 整改到可发布的 main。默认只读审计；获得修复授权后只在 dev 改代码，最终发布只在 main 执行，不把测试通过等同于产物、人工或线上验收。
先确认权限边界
- 区分“准备”“修复”“打包”“发布”四种授权：
- 准备：只读检查、测试和普通构建。
- 修复：先给方案，dong4j 明确说“开干 / 改吧 / 实施”等之后才能写文件。
- 打包：只有当前消息明确要求时才能执行
scripts/package-*或产生分发产物。 - 发布：tag、push、上传、部署、公证提交、App Store 上传和 GitHub Release 各自需要当前任务明确授权。
- Changelog、普通版本文档、官网部署与
docs/功能实现总览.md使用各自独立授权；“准备发版”不自动授权写入或部署。 - 不删除数据库、不要求用户删库重建，不覆盖工作区中的无关修改。
选择当前阶段
dev准备 / 修复阶段：允许只读审计；获得修复授权后可修改代码、测试和发版文档。不得从dev打 tag、打正式包或发布。dev → main过渡阶段：全部自动门禁通过、工作区干净且获得分支操作授权后，才按现行分支规范合并并切换到main。发现分叉、未知修改或未跟踪文件时停止。main最终发布阶段：重新验证 HEAD、版本和工作区；获得对应授权后再执行 App Store / Direct 发布。若发现代码问题，返回dev修复，禁止直接在main开展日常整改。- 发布后文档收口阶段：公开版本事实确认后，区分已发布版本与下一待发布版本，审计整个 Starcat 目录下的独立仓库；获得文档授权后同步版本说明，官网部署仍需单独授权。
- 分支过渡、最终发布、本地 GitHub Release 和发布后文档收口的详细步骤读取 references/release-execution.md。
读取当前真值
在 Starcat 仓库根目录工作，并优先读取当前版本的下列文件，避免复制过时流程：
AGENTS.mdBRANCH.mddocs/功能实现总览.md（只读）docs/3-设计/详细设计/01-数据库设计.mddocs/5-规范/Git-分支与Worktree规范.mddocs/5-规范/Changelog-更新规范.mddocs/6-发版与上架/SOP-双渠道签名与发布.mddocs/6-发版与上架/SOP-手动发布命令清单.md
docs/6-发版与上架/SOP-发版流程.md 可用于理解历史版本机制，但双渠道命令和授权边界以上述现行 SOP 为准。
执行门禁
读取 references/gates.md，按顺序检查：
- 仓库、分支、worktree、dirty 状态和独立
supports/*仓库。 - 目标版本、上一个正式 tag、提交范围和远端 tag 冲突。
- 数据库迁移发布边界与同版本迁移收口。
- 四份 Changelog 的版本状态、双语和渠道差异。
- 单测、普通构建、脚本静态检查和必要的迁移测试矩阵。
- 获得授权后才检查分发产物、签名、公证、Store archive / 本地 export pkg 或 Direct DMG。App Store 正式包必须显式使用
/Applications/Xcode.app/Contents/Developer中的正式版 Xcode；Beta、RC 或 Preview 立即记为BLOCKED。Automatic Signing 的 archive 是中间产物；App Store 最终签名门禁以destination=export生成并解包验证的 pkg 为准。 - Direct 完整发布授权需包含 GitHub Release：先生成最终 DMG/SHA256 和本地 appcast，再由发布脚本通过本机 gh 上传、回读校验并公开附件，最后发布官网 appcast；不使用 GitHub Actions，也不再向阿里云上传 DMG/SHA256。
- 公开版本事实确认后读取 references/version-document-sync.md，审计并同步全工作区版本文档；不得把历史版本、兼容逻辑或下一待发布版本一起全局替换。
- 单独记录人工 UI、真实账户、升级迁移和线上发布验收。
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago Changed 3bd583d09dfe
- 24d ago First seen · 67 lines · 113 tokens per session scan A c2edd9f68f19
starcat-release-readiness is a skill published in the GitHub repository starcat-app/Starcat (202 stars, last pushed 5d ago), licensed MIT. It adds 113 tokens to every session and 1,379 once invoked, about $0.0005 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-09-23.
Other skills, from other repositories
release-note-captain
Use this skill when a project is finished, shipped, deployed, published, or released and the user wants a release note created or updated in Obsidian. It covers collecting release facts, choosing the note path, writing a concise release summary, updating existing notes safely, and preserving follow-up actions.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
release
Prepare, verify, and publish Sutando engine releases. Use when asked to prepare a release proposal, determine a version bump, audit release documentation, validate release gates, create a release PR, tag a confirmed release, or publish GitHub release notes. Preparation is safe and non-publishing; tagging and…
multi-repo-release
Prepares and validates GPT-RAG umbrella and multi-repository releases. Use whenever work involves release preparation, semantic versions, release branches, manifest or component pins, changelog release entries, tags, GitHub Release notes, or AI Landing Zone release alignment.