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 deadlinesgit 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/deadlines)<a href="https://agentmods.dev/skills/zhou210712/claude-for-legal-zh/deadlines"><img src="https://agentmods.dev/badge/skills/zhou210712/claude-for-legal-zh/deadlines/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/deadlines"><img src="https://agentmods.dev/badge/skills/zhou210712/claude-for-legal-zh/deadlines.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.00091 | $0.02384 |
| Opus 5 | $0.00046 | $0.01192 |
| Sonnet 5 | $0.00018 | $0.00477 |
| Haiku 4.5 | $0.00009 | $0.00238 |
Grade A, and why
deadlines 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
86% identical to client-intake — 255 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deadlines
- 加载
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md→ 管辖地、实践领域、预警天数节奏。 - 使用以下工作流。
- 按标志路由：
--add：捕获案件、类型、描述、截止日期、来源、负责人。写入~/.claude/plugins/config/claude-for-legal/legal-clinic/deadlines.yaml。先检查重复。--report（默认）：跨案汇总——逾期、未来3天、未来7天、未来14天；按负责人；按实践领域；未分配标记。--update [id]：修改字段；记录带日期的备注。--complete [id]：标记完成；与学生确认工作已实际提交/送达。--close [id]：未完成即关闭；需在备注中写明理由。
- 任何写入前先确认。
截止日期
目的
诊所最大的运营风险是错过截止日期。学生同时处理多个案件、兼职工作、每学期更替。仅存于个别学生脑海中的截止日期在交接时被遗漏，在期末考试周被遗忘，在学生意外退出诊所时被错过。本技能是集中的运营记录。
一旦错过截止日期，指导律师承担责任。技能按此风险级别校准——预警提前触发，逾期项目在明确解决前保持可见，交接（通过 /semester-handoff）将截止日期列表向前传递给下一位学生。
加载上下文
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md→ 管辖地、实践领域、截止日期预警天数（默认14/7/3/1）、指导律师~/.claude/plugins/config/claude-for-legal/legal-clinic/deadlines.yaml——分类台账
管辖地假设。 截止日期计算和预警阈值假设 CLAUDE.md 中设定的管辖地。截止日期、中断/延长规则、期间计算规则和本地法院惯例在不同省份和具体法院之间存在实质差异。如果事项涉及不同省份、特定法院的本地规则或法院层级问题，在依赖之前与你的指导老师对照管辖规则确认截止日期。
模式
标志：--add | --report | --update | --complete | --close（默认：report）
--add ——记录一个新截止日期
输入：
- 案件编号 + 名称（哪个案件）
- 实践领域
- 类型：答辩期 / 庭审 / 诉讼时效 / 举证期限 / 上诉期 / 申请执行期 / 行政复议 / 其他
- 描述——一行说明应完成事项
- 截止日期（如适用含时间和时区）
- 来源——截止日期从哪里来（法院传票日期、法条依据如《民法典》第188条、《民事诉讼法》第128条）
- 负责学生——负责的学生姓名
技能自动生成 id 标识：[案件]-[简短描述]-[YYYY-MM]。
从其他技能中提取： 当 /client-intake、/draft 或 /status 在其输出中浮现截止日期时，应预填充字段移交至本技能。学生确认并添加。
添加前检查： 如果存在相同 case_id + type + due_date 的截止日期，标记为可能重复并在添加前询问。
合理性检查带。 学生输入截止日期后，不要计算或核实——但对照该递交类型的典型范围进行粗略的合理性检查，如果日期远在范围之外则标记学生。这是帮助学生自查算术中重大错误的支架，而非替代对照规则计算。
检查带按管辖地设置。 从 references/plausibility-bands/{省份}.md 加载本诊所管辖地的检查带文件。如果管辖地的检查带文件在冷启动时不存在，在本会话中每个条目均写入 warnings: no-plausibility-band，并告知指导老师如何建立检查带文件。
合理性检查逻辑：
- 加载本诊所管辖地的检查带表（外加始终适用的全国性期间）。
- 在学生输入
due:后，与该递交类型的典型范围比较。 - 如果在范围内，写入条目。不说什么——检查带是为了捕捉错误，而非庆祝正确的计算。
- 如果明显超出范围，在写入前停止并提示重新检查。
- 如果该类型的检查带未知（不常见的递交类型），不进行合理性检查。
本技能不计算截止日期。 如果学生在 due: 字段中输入 [需核实] 因为他们还没做计算，则以 due: [需核实] 写入条目——合理性检查带仅在学生提供具体日期时才运行。计算仍由学生和指导老师完成。
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 · 164 lines · 91 tokens per session scan A 088038f5d073
deadlines 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 91 tokens to every session and 2,384 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to client-intake, differing in 255 lines, and is treated as a copy.
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.