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 lordmos/dev-crew --skill crew-checkpointgit clone --depth 1 https://github.com/lordmos/dev-crewWrote 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/lordmos/dev-crew/crew-checkpoint)<a href="https://agentmods.dev/skills/lordmos/dev-crew/crew-checkpoint"><img src="https://agentmods.dev/badge/skills/lordmos/dev-crew/crew-checkpoint/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/lordmos/dev-crew/crew-checkpoint"><img src="https://agentmods.dev/badge/skills/lordmos/dev-crew/crew-checkpoint.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.00030 | $0.00639 |
| Opus 5.5 | $0.00012 | $0.00256 |
| Sonnet 5.5 | $0.00006 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
crew.checkpoint 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.
What it actually says
crew checkpoint — 阶段审计与一致性检查
Pre-flight Check
Run the check.sh script in this skill's directory:
- If
STATUS: NOT_INITIALIZED→ Stop. Tell the user: "DevCrew 工作区尚未初始化，请先运行 /crew.init" - If
STATUS: INITIALIZED→ Use the output as workspace context. Proceed below.
对当前活跃变更执行阶段审计，检查所有审计项是否通过，确保一致性后推进到下一阶段。
何时使用
- 每个 PDEVI 阶段结束时必须执行
- 用户说"做个检查点"、"检查一下"、"run checkpoint"
- 需要验证当前阶段的产出质量
使用方法
CLI
npx @lordmos/dev-crew checkpoint [change-name]
不指定变更名称时，自动选择第一个活跃变更。
MCP Tool
crew_checkpoint(cwd: string, change?: string)
审计清单
Plan 阶段
- proposal.md 包含目标、需求、验收标准
- 验收标准为 checklist 格式（
- [ ]） - 命名一致性检查
- 用户已确认（
plan_confirmed: true）
Design 阶段
- design.md 引用 proposal.md（文件指针，非重复内容）
- 技术决策附带理由
- 任务分解为 checklist 格式
- 任务分解覆盖所有验收标准
- 命名与 proposal 一致
Execute 阶段
- impl-log.md 所有任务标记
[x] - 每条完成记录附带文件路径和改动摘要
- 代码改动与 design.md 任务一一对应
- 无未完成的 design.md checklist 项
Verify 阶段
- test-report.md 逐条检查验收标准
- review-report.md 完成代码审查
- 缺陷记录附带回退建议
- 用户已确认（
verify_confirmed: true）
一致性审计
除阶段审计外，还检查：
- blockers.md 是否有
[OPEN]状态的阻断项 - resume.md 是否存在且格式正确
- 文件是否超过 200 行（建议拆分或使用文件指针）
输出
审计报告包含 [PASS] / [TODO] 标记、一致性检查结果、记忆同步提醒和下一阶段建议。
What ships with it
1 file 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.
- 1mo ago First seen · 87 lines · 30 tokens per session scan A 1591e3be2d66
crew.checkpoint is a skill published in the GitHub repository lordmos/dev-crew (11 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 639 once invoked, about $0.0001 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-31.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…