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 agentmods add commands/dhslegen/digital-delivery-team/packagegit 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/package)<a href="https://agentmods.dev/commands/dhslegen/digital-delivery-team/package"><img src="https://agentmods.dev/badge/commands/dhslegen/digital-delivery-team/package.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 | $0.00019 | $0.01678 |
| Opus 5 | $0.00010 | $0.00839 |
| Sonnet 5 | $0.00004 | $0.00336 |
| Haiku 4.5 | $0.00002 | $0.00168 |
Grade B, and why
package 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 4d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/package
输入:$ARGUMENTS
Phase 1 — 前置校验
以下任一不满足直接拒绝:
test -f tests/test-report.md || { echo "❌ tests/test-report.md 不存在,请先运行 /test"; exit 1; }
test -f docs/review-report.md || { echo "❌ docs/review-report.md 不存在,请先运行 /review"; exit 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 package --inputs "docs/prd.md,docs/arch.md,web/,server/" --outputs "README.md,docs/deploy.md,docs/demo-script.md" --next "/report"
exit 0
fi
node "$DDT_PLUGIN_ROOT/bin/emit-phase.mjs" --phase package --action start
"$DDT_PLUGIN_ROOT/bin/check-blockers.sh" || exit 2
# v0.9.20 D36:部署事实采集——扫 application*.yml / pom.xml / package.json / docker-compose
# 输出 .ddt/deployment-facts.json(docs-agent 必读)+ docs/deployment-facts.md(人读)
# docs-agent 在生成 deploy.md 时**禁止凭常识**填硬编码 root/actuator,必须用本文件的事实
node "$DDT_PLUGIN_ROOT/bin/audit-deployment-config.mjs" 2>&1 || echo "⚠️ deployment audit 失败(不阻塞,docs-agent 会用占位提示用户补全)"
若 docs/review-report.md 中阻塞级条目 > 0,拒绝执行并提示:
❌ 存在阻塞级问题,请修复后重跑
/review
Phase 2 — 派发 docs-agent
使用 Task 工具派发 docs-agent,传入:
docs/prd.md(产品需求文档)docs/arch.md(架构决策,若存在)$DDT_PLUGIN_ROOT/templates/deploy.template.md(部署模板,插件根——v0.9.3 D19)$DDT_PLUGIN_ROOT/templates/demo-script.template.md(演示脚本模板,插件根)$ARGUMENTS(如--demo-length 5)
docs-agent 产出:
| 产出文件 | 说明 |
|---|---|
README.md |
项目主文档,含功能概述、快速启动 |
docs/deploy.md |
一键部署指南,含环境要求和步骤 |
docs/demo-script.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.
- 4d ago First seen · 157 lines · 19 tokens per session scan B 213b0146e01a
package is a command published in the GitHub repository dhslegen/digital-delivery-team (1 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 1,678 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
negative-keyword-sweep
Find wasted spend in Google Ads search terms and add negatives at the right scope (account list, campaign, or ad group). Use when the user says "find junk keywords", "stop wasting on bad searches", or wants a search-terms cleanup.
import
Import a shared context bundle, or take a teammate's newer copy of one you already have.
launch-meta-campaign
Launch a complete Meta Ads campaign — campaign, ad set, and ad(s) — built paused and ready to review. Use when the user wants a new Facebook/Instagram campaign.
create-topic
Research and generate a complete topic plan with keyword mapping, audience, angle, and competitive positioning.
extensions
Show what the connected context expects to reach, and whether this machine provides it.
list
List the NeatContext contexts you can connect.