verify

verify is a command for coding agents from dhslegen/digital-delivery-team. It costs 18 tokens per session (519 once invoked), scanned A, original, MIT.

A verification command that runs a test agent and a code-review agent in the same round, then combines their results.

In plain words
What is it for?
Use it after the required product and API design files exist to run tests, check test coverage, review code against the main branch, and decide whether shipping is allowed.
Why use it?
It checks both whether the code works and whether reviewers found serious problems before delivery continues.

Command

Part of the digital-delivery-team plugin — 13 skills, 21 commands, 9 agents, 8 hooks shipped together

Install

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.

agentmods
npx agentmods add commands/dhslegen/digital-delivery-team/verify
Clone the repo
git clone --depth 1 https://github.com/dhslegen/digital-delivery-team

Or install digital-delivery-team, the plugin that ships this one along with the rest of its 13 skills, 21 commands, 9 agents, 8 hooks.

Wrote 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.

agentmods badge for verify

README.md
[![agentmods](https://agentmods.dev/badge/commands/dhslegen/digital-delivery-team/verify.svg)](https://agentmods.dev/commands/dhslegen/digital-delivery-team/verify)
Your own site
<a href="https://agentmods.dev/commands/dhslegen/digital-delivery-team/verify"><img src="https://agentmods.dev/badge/commands/dhslegen/digital-delivery-team/verify.svg" alt="Measured on agentmods" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 519 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.00519
Opus 5 $0.00009 $0.00260
Sonnet 5 $0.00004 $0.00104
Haiku 4.5 $0.00002 $0.00052

Measured 5d ago against content hash ae6e322e810a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

verify 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 5d 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.

commands/verify.md · 61 lines

What it actually says

/verify


关键约束

同一条消息内同时发出两个 Task 工具调用:

  • Task 1test-agent(执行测试 + 覆盖率)
  • Task 2review-agent(代码评审,基线 main

前置校验

test -f docs/prd.md           || { echo "❌ 请先运行 /prd"; exit 1; }
test -f docs/api-contract.yaml || { echo "❌ 请先运行 /design"; exit 1; }

# v0.9.11 D28 软提醒:建议先 /integrate 起栈联调,让 /verify 跑在真实栈上
if [ ! -f docs/integrate-report.md ]; then
  echo "ℹ️  建议先跑 /digital-delivery-team:integrate 起栈联调(db + redis + 前后端 + smoke)"
  echo "   未跑 /integrate 时 test-agent 仅跑 unit + 契约校验,不验证真实集成。"
  echo "   仅后端 API / 别个单元项目可忽略。"
fi

两者都完成后汇总

读取 tests/test-report.mddocs/review-report.md,判断放行条件:

指标 放行条件
覆盖率 ≥ 70%
阻塞级评审项 = 0

任一不满足

禁止推进到 /ship,建议下一步:

  • 阻塞级 > 0 时:/fix --severity blocker --apply 修复后重跑 /verify
  • 覆盖率不足时:补充测试用例后重跑 /test
/verify 完成

覆盖率:        <coverage>%  ✅ / ❌
阻塞级评审项:  <n> 条       ✅ / ❌
警告级评审项:  <n> 条
建议级评审项:  <n> 条

若全部放行:

✅ 建议下一步:/ship

$ARGUMENTS

Changes

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.

  1. 5d ago First seen · 61 lines · 18 tokens per session scan A ae6e322e810a

Subscribe to this mod's changes

verify is a command published in the GitHub repository dhslegen/digital-delivery-team (1 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 519 once invoked, about $0.0001 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-31.