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 deposition-prepgit 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/deposition-prep)<a href="https://agentmods.dev/skills/zhou210712/claude-for-legal-zh/deposition-prep"><img src="https://agentmods.dev/badge/skills/zhou210712/claude-for-legal-zh/deposition-prep/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/deposition-prep"><img src="https://agentmods.dev/badge/skills/zhou210712/claude-for-legal-zh/deposition-prep.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.00080 | $0.01440 |
| Opus 5 | $0.00040 | $0.00720 |
| Sonnet 5 | $0.00016 | $0.00288 |
| Haiku 4.5 | $0.00008 | $0.00144 |
Grade A, and why
deposition-prep 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 9d 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
89% identical to brief-section-drafter — 159 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.
What it actually says
/deposition-prep
- 加载
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md→ 案件理论、关键事实。 - 遵循以下工作流和参考材料。
- 提取证人撰写或被提及的文件。
- 构建提纲:背景、关键文件、与理论相关的要点、质证材料。
庭前准备(含庭审提纲)
目的
一份庭前提纲是一张地图:背景 → 锁定有利事实 → 用不利事实对质 → 围绕理论控制范围。本技能从文件和案件理论构建这张地图。
记录保真——引用和精确定位
两条规则管理从案卷中提取到本提纲的每个引用和每个引文。
逐字引用必须逐字。 除非你有确切的段落并可以引用到它,不要对对方律师、证人、法庭或任何案卷文件的话语加引号。当你想表征某人说的话但找不到确切措辞时:
- 无引号转述,明确归因。
- 标记占位符:
[核实确切引文——案卷引用待定] - 绝不填补空白。 一个编造的先前陈述在证人否认且笔录不支持你时摧毁质证。
精确引用必须支持整个命题。 如果一个质证点是"证人在[日期]说了X、Y和Z",核实精确引用支持X和Y和Z。
加载上下文
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → 案件理论。
工作流
步骤1:证人是谁?
- 姓名、角色、与案件的关系
- 我们为什么需要其出庭作证——我们需要从该证人获得什么?
步骤1a:证人立场——起草问题前先分叉
准备结构因立场不同而异:
- 对方/不利证人——交叉询问风格:封闭式、引导式、一次一个事实。构建框架。
- 己方/有利证人——直接询问风格:开放式问题让证人讲故事。与己方证人使用封闭式引导问题通常不适当。
- 中立第三方——混合;通常开放式获取故事,封闭式锁定具体内容。
- 单位当事人(《民事诉讼法》司法解释相关规定)——单位的法定代表人、负责人或工作人员代表单位接受询问。确认民事诉讼法及司法解释关于当事人陈述的规定。
步骤2:提取其文件
从案件材料中:
- 证人撰写的文件
- 发送给证人或由证人发送的文件
- 提及证人姓名的文件
- 证人参加的会议记录
步骤3:构建要点
每个要点是你想确立或探究的事项。围绕理论组织:
背景(始终最先——在证人防御之前锁定无争议事实):
- 角色、任期、职责
- 汇报关系
- 如何与关键参与者互动
有利事实(在对质前锁定):
- 该证人可以确立的、支持己方理论的事实
- 证人撰写或收到的、支持己方理论的文件
不利事实(用文件对质):
- 对方无论如何会问及的、对己方不利的事实——先获取己方版本
- 有伤害的文件——知道证人将如何解释它们
质证材料(如对方或如存在矛盾):
- 先前的矛盾陈述(来自文件、先前证言、书面陈述)
- 与你预期其将说的内容矛盾的文件
核心事实:
- 确立(或削弱)案件依赖于的事实的提问序列
步骤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.
- 9d ago First seen · 148 lines · 80 tokens per session scan A bf415df681a4
deposition-prep 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 80 tokens to every session and 1,440 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to brief-section-drafter, differing in 159 lines, and is treated as a copy.
Other skills, from other repositories
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…