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 integration-managementgit 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/integration-management)<a href="https://agentmods.dev/skills/zhou210712/claude-for-legal-zh/integration-management"><img src="https://agentmods.dev/badge/skills/zhou210712/claude-for-legal-zh/integration-management/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/integration-management"><img src="https://agentmods.dev/badge/skills/zhou210712/claude-for-legal-zh/integration-management.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.00111 | $0.06221 |
| Opus 5 | $0.00056 | $0.03111 |
| Sonnet 5 | $0.00022 | $0.01244 |
| Haiku 4.5 | $0.00011 | $0.00622 |
Grade A, and why
integration-management 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 12d 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 — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/integration-management
- 加载
deal-context.md获取交易代码、目标公司、交割日期、交易负责人。 - 加载
integration-tracker.yaml（如存在；或通过 --init 创建）。 - 使用以下工作流。
- 按标志路由：
--init：模式1——读取收购协议，构建分阶段工作计划、同意追踪器--contracts：模式2——导入合同清单（存储库或上传），分层和分类--report：模式3——生成状态报告--update：模式4——手动更新或解析上传的状态文件--export：模式5——CSV 或表格导出
- 读取/写入
~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[代码]/integration-tracker.yaml。 - 任何写入后：展示变更摘要并呈现任何新标记。
事项上下文
事项上下文。 检查实务级 CLAUDE.md 中的 ## 事项工作区。如果 Enabled 为 ✗（企业法务用户的默认值），跳过本段其余内容——技能使用实务级上下文，事项机制不可见。如果已启用且无活跃事项，询问："这是哪个事项？运行 /corporate-legal:matter-workspace switch <事项简称> 或说 实务级。"加载活跃事项的 matter.md 获取事项特定上下文和覆盖规则。输出写入事项文件夹 ~/.claude/plugins/config/claude-for-legal/corporate-legal/matters/<事项简称>/。除非 跨事项上下文 为 开，否则绝不读取其他事项的文件。
目的
外部律师交割交易。法务继承混乱。本技能是交割后整合的项目管理层——不是业务整合，不是IT系统，不是HR组织设计。是法律工作流：同意事项、合同转让、主体合理化、知识产权登记、股权收购协议义务。它追踪什么已完成、什么待到期、什么在受阻以及什么需要决策。
追踪器文件
存放于 ~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[代码]/integration-tracker.yaml。读取 deal-context.md 获取交易代码、目标公司名称、交割日期和交易负责人。从 closing-checklist.yaml（如存在）继承任何交割后项目。
# integration-tracker.yaml
metadata:
deal_code: "[代码]"
target: "[公司名称]"
close_date: "[YYYY-MM-DD]"
deal_lead: "[姓名]"
outside_counsel: "[律所和牵头律师]"
last_updated: "[日期]"
last_status_report: "[日期 或 空]"
pa_dates:
required_consents_deadline: "[YYYY-MM-DD — 从收购协议中提取]"
rep_survival_expires: "[YYYY-MM-DD]"
escrow_release: "[YYYY-MM-DD 或 空]"
earnout_milestones:
- description: "[里程碑]"
measurement_date: "[YYYY-MM-DD]"
payment_date: "[YYYY-MM-DD]"
owner: "finance" # 始终为财务——法务仅追踪日期
workplan:
day_1:
target_date: "[close_date + 7天]"
items: []
day_30:
target_date: "[close_date + 30天]"
items: []
day_90:
target_date: "[close_date + 90天]"
items: []
day_180:
target_date: "[close_date + 180天]"
items: []
required_consents: []
desired_consents: []
contracts:
source: "[存储库 / manual-upload / disclosure-schedule]"
repository_path: "[路径 或 空]"
last_imported: "[日期]"
total: 0
tier_1: []
tier_2: []
tier_3: []
tier_4: []
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.
- 12d ago First seen · 493 lines · 111 tokens per session scan A a8ede8880495
integration-management is a skill published in the GitHub repository zhou210712/claude-for-legal-ZH (212 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 111 tokens to every session and 6,221 once invoked, about $0.0006 per session on Opus 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…
integration-management
Post-closing M&A integration tracker — phased workplan, consent tracking, contract assignment at scale, weekly status reports. Initializes from whatever deal artifacts are available (purchase agreement, deal summary, closing checklist) and connects to deal-context.md and closing-checklist.yaml from the M&A cold-start.…
matter-workspace
Manage matter workspaces — new, list, switch, close, or detach (practice-level). File-management logic for keeping one client or engagement's context separate from every other. Use when working across multiple clients or matters, when the user says "new matter", "switch matter", "list matters", "close matter", or when…
patent-docket
A workflow coordinator for patent case files, from an inventor's technical disclosure to patent application documents. A patent docket is the tracked record of a patent matter, including its stage, questions, drafts, and handoffs.
performance-management
Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.