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-retrogit 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-retro)<a href="https://agentmods.dev/skills/arch-team/devpace/pace-retro"><img src="https://agentmods.dev/badge/skills/arch-team/devpace/pace-retro/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-retro"><img src="https://agentmods.dev/badge/skills/arch-team/devpace/pace-retro.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.00117 | $0.01457 |
| Opus 5.5 | $0.00047 | $0.00583 |
| Sonnet 5.5 | $0.00023 | $0.00291 |
| Haiku 4.5 | $0.00012 | $0.00146 |
Grade A, and why
pace-retro 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pace-retro — 迭代回顾与度量
生成迭代回顾报告，更新度量仪表盘，提供多粒度分析视角。详细执行规则见对应 procedures 文件。
与现有机制的关系
| 机制 | 职责 | 区别 |
|---|---|---|
| /pace-status metrics | 查看当前度量快照 | 只读展示，不做分析 |
| /pace-plan close | 迭代关闭时轻量回顾 | 3 个基准指标，不含改进建议 |
| /pace-retro | 完整回顾分析 + 经验沉淀 | 多维度分析 + 趋势对比 + 知识闭环 |
推荐使用流程
1. /pace-retro mid → 迭代中期快速检查（轻量，不影响基准线）
2. /pace-retro focus quality → 聚焦某个维度深入分析
3. /pace-retro → 迭代末尾完整回顾
4. /pace-retro accept → 确认回顾建议的操作（MoS 更新等）
5. /pace-retro compare → 对比本迭代与上一迭代的变化
6. /pace-retro history → 查看 3+ 迭代的趋势总览
7. /pace-retro update → 仅刷新度量数据（不生成报告）
输入
$ARGUMENTS：
- （空）→ 当前迭代完整回顾
update→ 仅刷新度量数据，不生成报告（带变化反馈）focus <维度>→ 聚焦回顾：quality | delivery | dora | defects | value | knowledge | epiccompare→ 对比回顾：当前迭代 vs 上一迭代的关键指标 deltahistory→ 趋势总览：跨 3+ 迭代的趋势线（基于 dashboard.md 历史快照）mid→ 中期检查：轻量版回顾，不更新 dashboard 基准线accept→ 确认回顾建议：执行 MoS 更新等上一次回顾建议的操作forecast→ 交付预测：基于历史模式预测迭代交付概率、识别瓶颈、发出风险预警
执行路由表
固定加载
| 文件 | 说明 |
|---|---|
skills/pace-retro/retro-procedures-common.md |
通用规则：§0 路由索引 · Agent 记忆 · 数据收集详情 · 基准线检测 |
按子命令加载
| 参数 | 额外加载文件 | 执行路径 |
|---|---|---|
| （空） | skills/pace-retro/retro-procedures.md + skills/pace-retro/retro-procedures-dimensions.md |
Step 1→2→3→4→5→6 完整回顾 |
update |
skills/pace-retro/retro-procedures-update.md |
Step 1→2（带变化反馈） |
focus <维度> |
skills/pace-retro/retro-procedures-focus.md |
单维度深入分析 |
compare |
skills/pace-retro/retro-procedures-compare.md（自包含，不加载 common） |
双迭代对比 |
history |
skills/pace-retro/retro-procedures-history.md（自包含，不加载 common） |
跨迭代趋势 |
mid |
skills/pace-retro/retro-procedures-mid.md（自包含，不加载 common） |
中期轻量检查 |
accept |
skills/pace-retro/retro-procedures-accept.md（自包含，不加载 common） |
执行建议操作 |
forecast |
skills/pace-retro/retro-procedures-forecast.md（自包含，不加载 common） |
交付预测分析 |
路由规则：只读取路由表映射的 procedures 文件，不加载其他文件。compare/history/mid/accept 自包含，不加载 common。
What ships with it
11 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.
- retro-procedures-accept.md 3.9 KB
- retro-procedures-common.md 4.0 KB
- retro-procedures-compare.md 4.3 KB
- retro-procedures-dimensions.md 17 KB
- retro-procedures-focus.md 8.6 KB
- retro-procedures-forecast.md 3.7 KB
- retro-procedures-history.md 5.0 KB
- retro-procedures-mid.md 4.7 KB
- retro-procedures-update.md 2.1 KB
- retro-procedures.md 6.9 KB
- scripts/compute-metrics.mjs 15 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 · 98 lines · 117 tokens per session scan A e19602c6da2f
pace-retro is a skill published in the GitHub repository arch-team/devpace (73 stars, last pushed 6mo ago), licensed MIT. It adds 117 tokens to every session and 1,457 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-08-30.
Other skills, from other repositories
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…
plan
Use this skill when performing structured project planning and PRD generation with three modes: new (project kickoff with repo scaffolding), feature (compact feature PRD), retro (data-driven retrospective). All modes share a researched Q&A engine that dispatches parallel Explore agents before each question wave…
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.…
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.
session-plan
Creates a structured wave execution plan with role-based assignment after user alignment. Decomposes agreed tasks into waves resolved from the session mode by scripts/session-shape.mjs, with optimal agent assignment, dependency ordering, and inter-wave checkpoints. Activated by session-start after Q&A phase completes.
session-start
Use this skill when initializing a session for any project repo. Autonomously analyzes git state, VCS issues, SSOT files, branches, environment, and cross-repo status. Then presents structured findings with recommendations before development wave planning, or an operations contract for explicitly requested…