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 zhou210712/claude-for-legal-ZH --skill closing-checklistgit clone --depth 1 https://github.com/zhou210712/claude-for-legal-ZHWrote 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/zhou210712/claude-for-legal-zh/closing-checklist)<a href="https://agentmods.dev/skills/zhou210712/claude-for-legal-zh/closing-checklist"><img src="https://agentmods.dev/badge/skills/zhou210712/claude-for-legal-zh/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/zhou210712/claude-for-legal-zh/closing-checklist"><img src="https://agentmods.dev/badge/skills/zhou210712/claude-for-legal-zh/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.00088 | $0.03046 |
| Opus 5.5 | $0.00035 | $0.01218 |
| Sonnet 5.5 | $0.00018 | $0.00609 |
| Haiku 4.5 | $0.00009 | $0.00305 |
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.
How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/closing-checklist
- 读取
~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[代码]/closing-checklist.yaml并使用以下模式。 - 如有状态更新:模式3(更新项目)。
- 否则模式4:阻碍项、关键路径、距交割天数。
事项上下文
事项上下文。 检查实务级 CLAUDE.md 中的 ## 事项工作区。如果 Enabled 为 ✗(企业法务用户的默认值),跳过本段其余内容——技能使用实务级上下文,事项机制不可见。如果已启用且无活跃事项,询问:"这是哪个事项?运行 /corporate-legal:matter-workspace switch <事项简称> 或说 实务级。"加载活跃事项的 matter.md 获取事项特定上下文和覆盖规则。输出写入事项文件夹 ~/.claude/plugins/config/claude-for-legal/corporate-legal/matters/<事项简称>/。除非 跨事项上下文 为 开,否则绝不读取其他事项的文件。
目的
当检查表完成时,交易交割。表上每一项,完成。无所遗漏。本技能维护清单,从尽调中发现的新项目并纳入,告诉团队什么在阻碍。
检查表
存放于 ~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[代码]/closing-checklist.yaml。结构:
deal_code: "Project Falcon"
target_close: [日期]
signing_date: [日期]
last_updated: [日期]
conditions_precedent:
- id: CP-001
item: "经营者集中审查等待期届满"
category: "监管审批"
responsible: "买方律师"
due: 2026-04-15
status: "已于2026-03-01申报,等待期进行中"
blocking: true
source: "股权收购协议 §7.1(a)"
- id: CP-002
item: "Acme Corp 同意合同转让"
category: "第三方同意"
responsible: "目标公司 — 张三"
due: 2026-04-20
status: "请求已于2026-03-10发出,无回应"
blocking: true
source: "清单 3.12(a)(4);Acme 主协议 §14.2"
closing_deliverables:
- id: CD-001
item: "目标公司存续证明"
category: "公司"
responsible: "目标公司律师"
due: 2026-04-28
status: "未开始"
blocking: true
source: "股权收购协议 §2.3(b)(iv)"
# ... 等等
模式
模式1:从股权收购协议初始化
阅读已签署(或接近定稿)的股权收购协议。提取:
- 每项交割先决条件(位置因协议而异——阅读实际的条款标题)
- 每项交割交付物(交割交付物清单或相应条款)
- 每项含交割前截止日的承诺
每项均成为检查表项目,附协议条款的来源引用。
填充监管/审批项前的研究义务。 反垄断、外商投资和行业特定审批(例如经营者集中申报、外商投资安全审查、行业监管部门审批)具有因法域而异的操作机制、阈值和时间窗口,且会变化。从收购协议中提取每项监管条件的名称,然后研究当前有效的操作机制(谁来申报、何时、什么触发二次审查、等待期多长)。引用一级来源并核实时效性。不要凭记忆填充时间假设 [yuandian检索]。
重大不利影响/重大不利变化交割条件。 从收购协议中提取定义术语——重大不利影响/重大不利变化的措辞是谈判形成的结果,不是标准模板。在将某一事件标记为可能的重大不利影响/重大不利变化触发条件前,研究管辖法律下对所用具体语言的理解(不同法域对待例外条款和量化检验的方式不同)。
从重大合同中提取同意要求 取决于管辖法律的默认规则和各合同中具体的禁止转让表述。逐份合同研究适用规则而非假设一个默认规则 [yuandian检索]。
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 · 206 lines · 88 tokens per session scan A c4bae18e8e06
closing-checklist is a skill published in the GitHub repository zhou210712/claude-for-legal-ZH (238 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 88 tokens to every session and 3,046 once invoked, about $0.0004 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-30.
Other skills, from other repositories
vendor-review
Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.
entity-compliance
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity…
portfolio
Track the IP portfolio — registrations, renewals, maintenance fees, and use declarations. Use when checking what's renewing, adding or updating an asset, recording a maintenance filing, or auditing the register for gaps, lapses, and use-in-commerce questions. Receives handoffs from prosecution and clearance work.
launch-review
Full launch review against your framework and risk calibration. Use when the user says "review this launch", "legal review for [feature]", "can we ship this", "what are the legal issues with [product]", or references a launch tracker ticket or PRD that needs a category-by-category review memo.
client-intake
Structured intake — practice-area templates, cross-area issue spotting, conflict flags, and triage classification. Produces a formatted case summary the student analyzes and the professor reviews. Does NOT decide case acceptance. Use when starting a new client intake, running an intake interview, or writing up a new…
gap-surfacer
Reference: shared gap- and comment-tracker framework backing /regulatory-legal:gaps and /regulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by…