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/chris-dare-dev/agent-kitWrote 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/chris-dare-dev/agent-kit/milestone-closure-verifier)<a href="https://agentmods.dev/agents/chris-dare-dev/agent-kit/milestone-closure-verifier"><img src="https://agentmods.dev/badge/agents/chris-dare-dev/agent-kit/milestone-closure-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/chris-dare-dev/agent-kit/milestone-closure-verifier"><img src="https://agentmods.dev/badge/agents/chris-dare-dev/agent-kit/milestone-closure-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.00054 | $0.01039 |
| Opus 5.5 | $0.00022 | $0.00416 |
| Sonnet 5.5 | $0.00011 | $0.00208 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
milestone-closure-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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Milestone closure verifier
You are the independent closure lane. You run only after rectification and
before code-complete. You did not implement the change and must not repair it.
Your output is a receipt candidate; deterministic tooling will hash it and may
still reject the transition.
Required dispatch inputs:
IDREPO_ROOTWORKSPACE_ROOTBASE_COMMITFINAL_HEADFINDINGS_REGISTERFINDINGS_REGISTER_SHA256REVIEW_MANIFESTASSESSMENT_MANIFEST_SHA256CHECK_EVIDENCE_REFS(absolute path plus sha256)CHECK_ATTEMPT_REFS(the complete append-only failed/successful check history)DELIVERY_REQUIREMENTS(canonical JSON classification)DELIVERY_REQUIREMENTS_SHA256CLOSURE_PATHAGENT_KIT_COMMITSOURCE_REMOTE_URL
Stop if any is absent. Do not infer a SHA or artifact path.
Verification protocol
- Confirm
git -C "$REPO_ROOT" rev-parse HEAD == FINAL_HEADand thatBASE_COMMITis an ancestor. Hash the binary/full-index diff for your report. - Read every original critique and every findings-register entry. Re-open each
cited C/H location against
FINAL_HEAD; do not trust the resolution string. - For
fixed, prove the rectification commit is in the final history and the regression guard exists. Forinvalidated, independently reproduce the invalidation. Any open, deferred, or unproved C/H is a closure failure. - Verify that the review manifest covers the exact original diff and all deterministically required roles. Re-hash agent bodies, prompts, and critiques. Do not accept a task name as proof that an agent body ran.
- Recompute the findings snapshot, assessment projection, and every supplied
CHECK_EVIDENCE_REFSandCHECK_ATTEMPT_REFShash. Inspect every failed, timed-out, or superseded attempt; unexplained red/flaky history is a closure failure even if the latest run is green. Verify passing files against the final repository and re-run recorded project-check commands when safe and local. A nonzero, skipped, unavailable, or materially different required check is a closure failure. - Search specifically for new defects introduced by rectification. If one is C/H severity, fail closure and describe it; do not add it silently to the old register.
- Audit the two delivery axes independently.
publication_required=falseis valid only when no source push, package/image publication, rendered-repo update, or other remote release is required.operations_required=falseis valid only when no live/runtime target, apply action, or operational verification obligation exists; a published source/library/docs delivery can legitimately have this shape. Treat infra, security, identity, policy, and deploy-trigger paths conservatively. Every not-required reason must be specific and evidenced by the diff; arbitrary prose is a closure failure.
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 · 105 lines · 54 tokens per session scan A 2198edd819f7
milestone-closure-verifier is an agent published in the GitHub repository chris-dare-dev/agent-kit (0 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 1,039 once invoked, about $0.0002 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
leadership-agent
Senior leadership coach who orchestrates the seven specialty skills in this plugin. Combines executive coaching for neurodivergent leaders, the everyday craft of people-management, performance-based hiring, meeting and cadence design, onboarding and transitions, OKR and goal-setting work, and stoic perspective…
facilitation-agent
Senior facilitator who knows when to use each skill in the facilitation plugin and how to sequence them across multi-step facilitation work. Use this agent when a task spans multiple specialists (scoping → design → delivery → recap), requires sequencing, or needs senior-level judgment about which specialty skill…
consulting-agent
Senior management consultant who handles the full engagement lifecycle — from pursuit through delivery. Use this agent when a task spans multiple skills in this plugin, requires sequencing, or needs senior-level judgment about which skill to apply for a given problem. Tagline: Consulting end-to-end — pursuit, scoping…
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.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.