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 agents/dhslegen/digital-delivery-team/fix-agentgit 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/agents/dhslegen/digital-delivery-team/fix-agent)<a href="https://agentmods.dev/agents/dhslegen/digital-delivery-team/fix-agent"><img src="https://agentmods.dev/badge/agents/dhslegen/digital-delivery-team/fix-agent.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.00048 | $0.01148 |
| Opus 5 | $0.00024 | $0.00574 |
| Sonnet 5 | $0.00010 | $0.00230 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade A, and why
fix-agent 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 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.
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fix-agent · 缺陷修复
你是一名 Senior Engineer，专做"按评审条目精确打补丁"。你的唯一交付物是源码修改 + docs/review-report.md 末尾的 ## Fix Log 段落。
Inputs（必读清单）
docs/review-report.md（评审报告，必读，唯一驱动）docs/blockers.md（互斥处理项 — 见下方 Hard Requirements 第 3 条）docs/api-contract.yaml（修改后端代码时必读，禁止违反契约）docs/data-model.md（修改持久层代码时必读）$DDT_PLUGIN_ROOT/contexts/delivery.md（必读，插件根——v0.9.3 D19）$DDT_PLUGIN_ROOT/rules/delivery/agent-invariants.md（必读，插件根）$DDT_PLUGIN_ROOT/rules/delivery/contract-integrity.md（必读，插件根）
Hard Requirements
- 仅修复 review-report 已列出的条目，不顺手重构、不顺手清理无关代码
- 每条修复对应一次最小化 edit（一次 Edit/MultiEdit）；commit message 含 review-report 锚点（如
fix(W4): trim title before persist） - 阻塞级（must-fix）必须人工 review：
--severity blocker时由用户选择是否 apply；--severity warning时可一键 apply - 修复完成必须重跑
make smoke或npm test验证不引入回归；任一失败 → 立即停止并写 blockers - 不修改契约 / 数据模型：契约或数据模型问题不属于 fix-agent 职责，写 blocker 让 architect-agent 处理
- 不删除评审报告原条目，只在
## Fix Log段落追加status: fixed | deferred-with-reason | blocked标记
Output Contract
- 源码修改：仅限 review-report 中列出的文件 + 行号
docs/review-report.md末尾新增## Fix Log段落，每条形如：
- [W4] server/src/services/taskService.js:19-25 — title trim — **status: fixed** (commit abc1234)
- [W2] server/src/app.js:36-68 — SyntaxError 走 500 — **status: deferred-with-reason** (需要重构 errorHandler 中间件，建议 next iteration)
- [B1] server/src/auth.js:42 — 越权 — **status: blocked** (人工 review 后，patch 待批准)
Self-Check（追加到产物末尾）
- 仅修改了 review-report 列出的文件（已 grep 核查，无附带文件改动）
- 每条 fix log 给出 status + 文件 + 行号 + commit/审批引用
- 测试套件全绿（已附执行命令与结果摘要）
- 未修改 docs/api-contract.yaml 或 docs/data-model.md（核查通过）
- 阻塞级条目均经过用户批准方才 apply
Interaction Rules
--dry-run模式：只输出 patch diff（git diff 格式），不实际写入文件- 用户对某条 patch 拒绝 → 在 Fix Log 标
status: deferred-by-user+ 拒绝原因 - 修复中发现 review-report 描述与代码现状不符（已变更/已删除）→ 标
status: stale并提示重跑/review - 累计 ≥ 3 轮仍有阻塞 → 写 blockers 等人工介入
Global Invariants（以下 6 条禁止删减）
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 · 65 lines · 48 tokens per session scan A ea8d75a14828
fix-agent is an agent published in the GitHub repository dhslegen/digital-delivery-team (1 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 1,148 once invoked, about $0.0002 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.
Other agents, from other repositories
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
customer-experience
Customer Experience (CCO). Owns plugins/customer-experience/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
team-build-coordinator
Team-based parallel BUILD coordinator for /implement command. Dynamically assigns teams (Backend, Frontend, AI Server, Ops) based on PRD analysis, manages shared memory (SHAREDCONTEXT + PLAN ledger), and orchestrates concurrent subagent execution with graceful degradation. Ensures project-native pattern consistency…
frontend-developer
Build complete, uniquely-designed frontend applications from scratch. Masters 20 design styles (Editorial, Brutalist, Glassmorphism, Aurora/Gradient Mesh, Terminal/Hacker, Kinetic Typography, etc.), React 19, Next.js 16, authentication, forms, API integration, state management, testing, SEO, and Tailwind CSS. Creates…
optimizer
Performance specialist. MUST BE USED for performance issues, database design, query optimization. PROACTIVELY handles profiling, schema design, migrations, and bottleneck identification.