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 | $0.00039 | $0.01367 |
| Sonnet 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 11d 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.
- 11d 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 3mo ago), licensed Apache-2.0. It adds 78 tokens to every session and 2,734 once invoked, about $0.0004 per session on Opus 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
import-sop
Import agency Standard Operating Procedures — approval workflows, campaign launch checklists, escalation procedures, QA steps — and structure them into numbered, role-assigned steps with human-approval gates marked. SOPs save at the agency level so they apply across every client brand, not per-brand. Triggers on…
chief-operating-officer
Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…
chief-information-officer
The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
chief-content-officer
Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists. Use this to build or fix a content production system, plan a calendar, decide how one piece becomes many, rank content ideas by expected impact, or audit…