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 skills add Buildwise-Studios/claude-for-hk-law --skill closing-checklistgit clone --depth 1 https://github.com/Buildwise-Studios/claude-for-hk-lawWrote 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/skills/buildwise-studios/claude-for-hk-law/closing-checklist)<a href="https://agentmods.dev/skills/buildwise-studios/claude-for-hk-law/closing-checklist"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/closing-checklist/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/skills/buildwise-studios/claude-for-hk-law/closing-checklist"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/closing-checklist.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.00078 | $0.02734 |
| Opus 5.5 | $0.00031 | $0.01094 |
| Sonnet 5.5 | $0.00016 | $0.00547 |
| Haiku 4.5 | $0.00008 | $0.00273 |
Grade A, and why
closing-checklist 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 1mo 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.
This is a copy
88% identical to closing-checklist — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/closing-checklist
- Read
~/.claude/plugins/config/claude-for-hk-law/corporate-legal/deals/[code]/closing-checklist.yamland use the modes below. - If status update provided: Mode 3 (update item).
- Otherwise Mode 4: blocking items, critical path, days to close.
Matter context
Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /corporate-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-hk-law/corporate-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
Purpose
Deals close when the checklist is done. Everything on it, done. Nothing missing. This skill maintains the list, ingests new items as they surface from diligence, and tells the team what's blocking.
The checklist
Lives at ~/.claude/plugins/config/claude-for-hk-law/corporate-legal/deals/[code]/closing-checklist.yaml. Structure:
deal_code: "Project Falcon"
target_close: [DATE]
signing_date: [DATE]
last_updated: [DATE]
conditions_precedent:
- id: CP-001
item: "HSR waiting period expiration"
category: "Regulatory"
responsible: "Buyer counsel"
due: 2026-04-15
status: "Filed 2026-03-01, waiting period runs"
blocking: true
source: "Purchase Agreement §7.1(a)"
- id: CP-002
item: "Acme Corp consent to assignment"
category: "Third-party consents"
responsible: "Target — Jane Doe"
due: 2026-04-20
status: "Request sent 2026-03-10, no response"
blocking: true
source: "Schedule 3.12(a)(4); Acme MSA §14.2"
closing_deliverables:
- id: CD-001
item: "Certificate of good standing — Target (DE)"
category: "Corporate"
responsible: "Target counsel"
due: 2026-04-28
status: "Not started"
blocking: true
source: "Purchase Agreement §2.3(b)(iv)"
# ... etc
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.
- 1mo ago First seen · 208 lines · 78 tokens per session scan A a39a5d2b9736
closing-checklist is a skill published in the GitHub repository Buildwise-Studios/claude-for-hk-law (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 78 tokens to every session and 2,734 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to closing-checklist, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
yearly-planner
Produce the Part 8 yearly planner: quarterly themes and monthly initiatives. "plan the whole year month by month".
20-brief-client-intake
Dung khi agency hoac freelancer nhan khach moi va can CHINH KHACH DIEN thong tin dau vao — form 11 phan ve san pham, muc tieu, ngan sach, kenh dang chay, doi thu, tai san san co, kem 20 ban toi uu theo tung nganh. Kich hoat khi user nhac 'brief khach hang', 'client intake', 'form khach dien', 'nhan khach moi', 'hoi…
64-team-brief-global
Use when a leader assigns work to a marketing team member or runs a cross-functional meeting — a task brief with concrete deliverables, a deadline with time and timezone, a definition of done, constraints, and check-in points, plus an async-first meeting agenda and action-item template. Trigger on 'assign a task'…
65-team-performance-review-global
Use when a leader evaluates a marketing TEAM MEMBER using data — a KPI scorecard by role, strengths with real examples, areas to improve stated as observable behavior, a 30 and 90 day development plan, and a 1-5 rating rubric. Trigger on 'performance review for my marketer', 'evaluate a team member', 'monthly 1:1…
64-team-brief
Dung khi can GIAO VIEC cho tung nguoi trong team marketing hoac chuan bi hop — task cu the, deadline theo gio, definition of done, rang buoc, diem check-in, kem template agenda va bien ban hop lien phong ban co action item. Kich hoat khi user nhac 'giao task cho team', 'brief cho nhan vien', 'phan cong cong viec'…
67-agency-vendor-brief
Dung khi thue NGUOI NGOAI lam — agency, freelancer, production house, vendor: scope of work, spec deliverable, so vong sua, quy trinh duyet, moc thanh toan, dieu khoan IP va bao mat, bang danh gia vendor sau du an. Kich hoat khi user nhac 'brief agency', 'thue freelancer', 'quan ly vendor', 'scope of work', 'agency…