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/arctan303/creator.skill/release-buildernpx skills add arctan303/creator.skill --skill release-buildergit clone --depth 1 https://github.com/arctan303/creator.skillWhat 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.00077 | $0.00592 |
| Opus 5 | $0.00039 | $0.00296 |
| Sonnet 5 | $0.00015 | $0.00118 |
| Haiku 4.5 | $0.00008 | $0.00059 |
Grade A, and why
release-builder 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 3d 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.
What it actually says
发布技能 (release-builder)
Purpose
把已验证代码转成可追溯、可复现、可回滚的交付物，并把本地发布准备与真实发布明确分开。
Trigger
- 开发完成，需要构建、打包、产物冒烟或发布准备报告。
- 用户要求部署或上线前检查。
- 仓库已有可识别的构建生态、版本来源或交付目标。
Required context
- 当前路线、交付契约、风险级别和审查结果。
- 仓库构建/打包配置、锁文件、CI 或 Wrapper 命令。
- 目标平台、产物形式、发布环境和回滚要求。
- 对真实推送、部署或上线的明确授权（如要执行）。
Workflow
- 从仓库文件识别生态和原生命令，不假设 npm 或固定技术栈。
- 检查版本、依赖锁定、构建入口、部署配置和审查门禁。
- 执行敏感信息与隐私审计，输出只包含 secret 名称和注入位置。
- 构建/打包后对最终产物执行与生态匹配的安装、启动或接口冒烟。
- 记录命令、结果、产物路径、失败/跳过项和回滚路径。
- 只有取得明确授权时才执行真实发布、推送或上线。
Output
- 发布准备状态与证据。
- 隐私/敏感信息审计结果。
- 构建、打包、产物冒烟和部署路径。
- 发布说明、阻塞项、授权记录与回滚方案。
Stop or escalate
- 真实秘密暴露、用户数据处理不清或构建失败：阻止发布。
- 找不到可复现构建入口：标记阻塞，不声明可发布。
- 测试或 reviewer 门禁缺失：列为发布阻塞。
- 未获得明确授权：只完成本地发布准备，不执行外部状态变更。
- 未授权部署不阻塞仍在授权范围内的构建、打包、产物冒烟和发布报告；只有用户目标必须真实上线时才请求授权并等待。
References
执行前读取 stage-contract.md。
What ships with it
2 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.
- 3d ago First seen · 52 lines · 77 tokens per session scan A 24cbc05ab724
release-builder is a skill published in the GitHub repository arctan303/creator.skill (20 stars, last pushed 29d ago), licensed MIT. It adds 77 tokens to every session and 592 once invoked, about $0.0004 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
prepare-providers-documentation
Replace the manual commit-by-commit classification step in breeze release-management prepare-provider-documentation with AI-driven classification. For each provider with pending changes, analyze every PR (batched into one sub-agent per provider, not one per PR), pay special attention to potentially breaking changes by…
sentry-fix-issues
Find and fix issues from Sentry using MCP. Use when asked to fix Sentry errors, debug production issues, investigate exceptions, or resolve bugs reported in Sentry. Methodically analyzes stack traces, breadcrumbs, traces, and context to identify root causes.
clawhub-production-release
Run and verify ClawHub production deploys and stable ClawHub CLI npm releases. Use when deploying backend or frontend changes to clawhub.ai, dispatching the Deploy workflow, publishing a stable CLI tag, checking release prerequisites, or proving the exact production SHA and workflow outcome.
hex-release
Guides interactive Hex package release for AgentJido repos. Supports automated (GitHub Actions workflowdispatch) and manual release flows. Uses gitops for version bumping and changelog generation. Triggers on: release, hex publish, bump version, new release, publish package.
agent-sop-author
Create (or update) and validate Agent SOPs (Standard Operating Procedures) - markdown-based workflows that guide AI agents through complex, multi-step tasks with RFC 2119 constraints.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.