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.
git clone --depth 1 https://github.com/dhslegen/digital-delivery-teamWrote 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/commands/dhslegen/digital-delivery-team/review)<a href="https://agentmods.dev/commands/dhslegen/digital-delivery-team/review"><img src="https://agentmods.dev/badge/commands/dhslegen/digital-delivery-team/review.svg" alt="Measured on agentmods" 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.00027 | $0.01634 |
| Opus 5 | $0.00014 | $0.00817 |
| Sonnet 5 | $0.00005 | $0.00327 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade B, and why
review scanned grade B with 1 finding 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 8d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
[ -f "$DDT_PLUGIN_ROOT/bin/aggregate.mjs" ] || DDT_PLUGIN_ROOT=$(cat "${HOME}/.claude/delivery-metrics/.ddt-plugin-root" 2>/dev/null) How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/review
输入:$ARGUMENTS(对比基线分支,默认 main)
Phase 1 — 校验
[ -f "$DDT_PLUGIN_ROOT/bin/aggregate.mjs" ] || DDT_PLUGIN_ROOT=$(cat "${HOME}/.claude/delivery-metrics/.ddt-plugin-root" 2>/dev/null)
[ -f "$DDT_PLUGIN_ROOT/bin/aggregate.mjs" ] || DDT_PLUGIN_ROOT="${HOME}/.claude/plugins/marketplaces/digital-delivery-team"
[ -f "$DDT_PLUGIN_ROOT/bin/aggregate.mjs" ] || { echo "❌ DDT plugin root 未解析。可能原因:(1) 插件未安装;(2) shell 中 DDT_PLUGIN_ROOT 指向无效路径,请 unset DDT_PLUGIN_ROOT 后重启会话;(3) 运行 /digital-delivery-team:doctor 自检"; exit 1; }
export DDT_PLUGIN_ROOT
if printf '%s' "$ARGUMENTS" | grep -q -- '--dry-run'; then
node "$DDT_PLUGIN_ROOT/bin/print-dry-run.mjs" --phase review --inputs "git diff <base>..HEAD,docs/prd.md,docs/arch.md" --outputs "docs/review-report.md" --next "/fix(如有 blocker) | /verify"
exit 0
fi
node "$DDT_PLUGIN_ROOT/bin/emit-phase.mjs" --phase review --action start
git rev-parse --is-inside-work-tree 2>/dev/null || { echo "❌ 非 git 仓库"; exit 1; }
BASE=${ARGUMENTS:-main}
git diff "$BASE"...HEAD --name-only | grep -q . || { echo "⚠️ 与 $BASE 无 diff,无需 review"; exit 0; }
# 检查上游阶段是否留下未解决 blockers
if [ -f docs/blockers.md ]; then
unresolved=$(awk '/^- \*\*resolved_at\*\*: null$/' docs/blockers.md | wc -l)
if [ "$unresolved" -gt 0 ]; then
echo "❌ docs/blockers.md 中存在 $unresolved 条未解决阻塞,请先处理。"
echo " 未解决项来自:"
awk '/^## /{h=$0} /^- \*\*resolved_at\*\*: null$/{print " - "h}' docs/blockers.md
exit 2
fi
fi
Phase 2 — 派发 review-agent
使用 Task 工具派发 review-agent,传入:
git diff $BASE...HEAD(完整差异)docs/arch.md(若存在)docs/api-contract.yaml(若存在)$DDT_PLUGIN_ROOT/templates/review-checklist.template.md(评审清单,插件根——v0.9.3 D19)$ARGUMENTS(对比基线)
review-agent 按三级分类产出 docs/review-report.md:
| 级别 | 含义 | 后续行动 |
|---|---|---|
| 阻塞 | 安全漏洞、数据丢失风险、逻辑致命错误 | 必须修复后重跑 /review |
| 警告 | 代码质量问题、缺失测试、性能隐患 | 建议修复 |
| 建议 | 可读性、命名、注释改进 | 可选 |
Phase 3 — 汇总输出
完成后向用户报告:
/review 完成
基线: <BASE> → HEAD
阻塞: <n> 条
警告: <n> 条
建议: <n> 条
报告: docs/review-report.md
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.
- 8d ago First seen · 155 lines · 27 tokens per session scan B e10e3b937bd8
review is a command published in the GitHub repository dhslegen/digital-delivery-team (1 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 1,634 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
review-pr
A command for reviewing a GitHub pull request, which is a proposed code change waiting to be merged. It examines the changes and can leave review comments or approve the pull request when the findings pass.
review-skills
Review changed skills: automated bash checks + 9 structural dimensions (D1-D9) + 5 intent checks (M1-M5). PASS/FAIL verdict. Fix in-place.
audit-project
Multi-agent code review with iterative improvement.
check
A combined code-quality review and design-to-implementation consistency check. It reads the changed files once, then evaluates them from both review perspectives.
pr-review
Reviews pull request changes to provide feedback, check for issues, and suggest improvements before merging into the main codebase.
code-review
Perform a comprehensive code review of recent changes.