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 arch-team/devpace --skill pace-releasegit clone --depth 1 https://github.com/arch-team/devpaceWrote 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/arch-team/devpace/pace-release)<a href="https://agentmods.dev/skills/arch-team/devpace/pace-release"><img src="https://agentmods.dev/badge/skills/arch-team/devpace/pace-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/arch-team/devpace/pace-release"><img src="https://agentmods.dev/badge/skills/arch-team/devpace/pace-release.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.00054 | $0.01245 |
| Opus 5.5 | $0.00022 | $0.00498 |
| Sonnet 5.5 | $0.00011 | $0.00249 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
pace-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 1mo 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pace-release — 发布管理
可选功能：如果你没有正式的发布流程，不需要使用这个命令。任务 merged 就是你的完成点，不需要 Release 管理。
管理 Release 生命周期：收集候选变更 → 创建 Release → 追踪部署 → 验证 → 关闭。支持 Changelog、版本 bump、Git Tag、GitHub Release、Release Notes 和发布分支管理。
推荐使用流程
标准发布： create → deploy → verify → close
快速查看： status（或无参数启动引导向导）
单步操作： changelog / version / tag / notes（独立使用）
回滚处理： rollback → 创建 hotfix CR → 新 create
历史回顾： status history
输入
$ARGUMENTS：
日常使用（大多数场景只需这些）：
create→ 创建新 Release（收集 merged CR + Gate 4 检查）deploy→ 记录部署操作（支持多环境晋升）verify→ 执行验证清单（支持自动化验证）close→ 完成发布（自动 changelog + 版本 bump + tag + 连锁更新）full→ close 的推荐别名（语义更明确）status→ 查看当前 Release 状态和建议下一步- （空）→ 引导式发布向导（推荐新用户使用）
单独使用（当你只需要其中某个步骤时）：
changelog→ 仅生成 CHANGELOG.mdversion→ 仅更新版本文件tag→ 仅创建 Git Tag / GitHub Releasenotes→ 生成面向用户的 Release Notes（按 Epic→BR→PF 组织，支持--role biz|ops|pm）branch→ 管理发布分支（创建 / PR / 合并）rollback→ 记录回滚（deployed 状态下出现严重问题时）status history→ 发布历史时间线（跨 Release 纵向视图 + DORA 趋势）
执行路由
根据子命令，只读取路由表中对应的 procedures 文件，不加载其他 procedures 文件。
核心操作固定加载
core 子命令（create/deploy/verify/close/full）加载 skills/pace-release/release-procedures-common.md（发布规则 + 集成规则 + 版本推断 SSOT）。
按子命令加载
| 参数 | 加载文件 | 说明 |
|---|---|---|
| （空） | skills/pace-release/release-procedures-wizard.md |
自包含；引导式向导（含 rolled_back 追踪） |
create |
skills/pace-release/release-procedures-common.md + skills/pace-release/release-procedures-create.md；CR>3 或有 config.md 时追加 skills/pace-release/release-procedures-create-enhanced.md |
分层加载 |
deploy |
skills/pace-release/release-procedures-common.md + skills/pace-release/release-procedures-deploy.md |
环境晋升 + 路径全景 |
verify |
skills/pace-release/release-procedures-common.md + skills/pace-release/release-procedures-verify.md |
自动健康检查 + 问题处理 |
close / full |
skills/pace-release/release-procedures-common.md + skills/pace-release/release-procedures-close.md；步骤 1-3 按执行进度加载 skills/pace-release/release-procedures-changelog.md / skills/pace-release/release-procedures-version.md / skills/pace-release/release-procedures-tag.md |
步进式增量加载 |
changelog |
skills/pace-release/release-procedures-changelog.md |
自包含 |
version |
skills/pace-release/release-procedures-version.md |
自包含（含精简版本推断规则） |
tag |
skills/pace-release/release-procedures-tag.md |
自包含 |
rollback |
skills/pace-release/release-procedures-rollback.md |
自包含（含候选预填） |
notes |
skills/pace-release/release-procedures-notes.md |
自包含（支持 --role biz|ops|pm） |
branch |
skills/pace-release/release-procedures-branch.md |
自包含 |
status / status history |
skills/pace-release/release-procedures-status.md |
自包含 |
What ships with it
16 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.
- release-procedures-branch.md 2.3 KB
- release-procedures-changelog.md 1.6 KB
- release-procedures-close.md 3.8 KB
- release-procedures-common.md 4.6 KB
- release-procedures-create-enhanced.md 7.0 KB
- release-procedures-create.md 3.2 KB
- release-procedures-deploy.md 2.7 KB
- release-procedures-notes.md 4.9 KB
- release-procedures-rollback.md 1.3 KB
- release-procedures-scheduling.md 2.0 KB
- release-procedures-status.md 2.2 KB
- release-procedures-tag.md 930 B
- release-procedures-verify.md 3.2 KB
- release-procedures-version.md 2.0 KB
- release-procedures-wizard.md 2.7 KB
- scripts/infer-version-bump.mjs 6.9 KB runs code
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.
- 1mo ago First seen · 79 lines · 54 tokens per session scan A fc5f38e24cb5
pace-release is a skill published in the GitHub repository arch-team/devpace (73 stars, last pushed 6mo ago), licensed MIT. It adds 54 tokens to every session and 1,245 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
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
github-project-management
GitHub project management with issue tracking, project-board automation, and sprint planning. Use when triaging or organizing issues, automating a project board, planning a sprint, or running release/roadmap coordination on GitHub.
gitlab-ops
Use this skill when performing VCS operations on GitLab or GitHub repositories — creating, updating, or closing issues and MRs, applying label taxonomy, running glab/gh CLI commands, or resolving project paths dynamically. Acts as the single source of truth for CLI command syntax and label conventions; consuming…
gitlab-portfolio
Use when you need a single-pane cross-repo health view across all vault-registered GitLab and GitHub projects. Discovers repos from overview.md frontmatter in /01-projects//, aggregates open issues, MRs, critical labels, and stale signals via parallel glab/gh calls, then writes an idempotent PORTFOLIO.md dashboard.…
npm-publish
Use when publishing this package to npm — a version release (npm publish), verifying the registry/pi.dev listing, or diagnosing npm auth failures (E403 2FA/token errors). Token-based flow via NPMTOKEN in .env.local with a temp userconfig, the leakage gate before every publish, post-publish verification and…
session-end
Use this skill when performing a full session close-out: verifies all planned work against the agreed plan, creates issues for gaps, runs quality gates, commits cleanly, mirrors to GitHub, and produces a session summary. Triggered by /close command.