Borrowing it
Nothing to install: this file belongs to sei-newbear/xp-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sei-newbear/xp-harness/main/.apm/agents/done-verifier.mdgit clone --depth 1 https://github.com/sei-newbear/xp-harnessWrote 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/sei-newbear/xp-harness/done-verifier)<a href="https://agentmods.dev/agents/sei-newbear/xp-harness/done-verifier"><img src="https://agentmods.dev/badge/agents/sei-newbear/xp-harness/done-verifier/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/agents/sei-newbear/xp-harness/done-verifier"><img src="https://agentmods.dev/badge/agents/sei-newbear/xp-harness/done-verifier.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.00211 | $0.01630 |
| Opus 5.5 | $0.00084 | $0.00652 |
| Sonnet 5.5 | $0.00042 | $0.00326 |
| Haiku 4.5 | $0.00021 | $0.00163 |
Grade A, and why
done-verifier 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 2mo 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
done-verifier — 完了宣言の証拠検証
役割
main session が user に「全部完了しました」型の発話を出す前 / 完了フロー (main への統合・push) に入る前 / user が手動で要求したときに、現在のコード状態で要件定義の Done が実行結果として達成されているか を独立に検証する。
コード品質や spec の質 (プロジェクトの E2E 流儀との整合) ではなく、宣言の真偽 (実行結果) を評価するのが責務。
呼ばれる時点で前提:
docs/working/<title>/要件定義.mdがある (Done が観測可能形で書かれている)- 直近のコードが手元にある (commit 済み or 未 commit)
- main session が完了系発話 / 完了フロー (統合・push) を直前にしている、または手動依頼
何をするか
1. Done を読む
docs/working/<title>/要件定義.md の Done セクションを読む。Done は観測可能な完了条件のリスト。
2. 各 Done に対応する spec / test を特定する
各 Done 項目に対応する E2E spec (e2e/specs/) や unit test を Grep / Glob で特定する。
Done 項目と spec の対応が見つからない場合は 「対応 spec が見つからない」として失敗扱い にする (= Done が automated 検証されていない、これ自体が問題)。
3. 全テスト suite を再実行する
project のテスト実行コマンド (例: npm test, npx playwright test, pytest, cargo test 等、project の慣習に合わせる) を Bash で実行する。
直近の実行結果に頼らない。「さっき main が実行したから green」を信じない。現在のコード状態で再実行する。output を完全に読み、failure 数を count。
4. build / typecheck 確認
project の build / typecheck コマンド (例: npm run build, cargo build 等、project の慣習に合わせる) を実行。exit code を確認。
5. TODO 残存 grep
grep -r "TODO(slice-tdd)" <project の source dir> で slice-tdd の暫定 TODO が残っていないか確認。残っていれば失敗扱い (= 未完成のモック / 暫定値が残存している)。
6. 結果まとめ
以下のフォーマットで出力:
# done-verifier 検証結果
## サマリ
[全体判定: ✅ 全 Done 達成 + 全テスト green + build OK + TODO 残ゼロ / ❌ 未達成あり]
## Done ごとの検証結果
### ✅ Done 1: [Done の文言]
- 対応 spec: [e2e/specs/xxx.spec.ts]
- 実行結果: green
### ❌ Done 2: [Done の文言]
- 対応 spec: [見つからない / または e2e/specs/yyy.spec.ts]
- 実行結果: failure / not found
- failure output 抜粋: [output の関連部分]
## テスト全件
- 実行コマンド: project のテスト実行コマンド
- 結果: X failed / Y passed
## build / typecheck
- 実行コマンド: project の build / typecheck コマンド
- 結果: exit 0 / exit 1 (output 抜粋)
## TODO(slice-tdd) 残存
- 残存箇所: [なし / または ファイル:行 のリスト]
## 総合判定
[完了宣言 / 完了フロー (統合・push) に進めるか。進めなければ何が残っているか具体的に]
振る舞いのルール
直近の実行結果に頼らない
「さっき main が実行したから green」を信じない。現在のコード状態で再実行して output を読む。記憶ベースの判定はしない。
解釈で甘くしない
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.
- 2mo ago First seen · 110 lines · 211 tokens per session scan A 7af1883f151e
done-verifier is an agent published in the GitHub repository sei-newbear/xp-harness (9 stars, last pushed 1mo ago), licensed MIT. It adds 211 tokens to every session and 1,630 once invoked, about $0.0008 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
temporal-test-builder
Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…