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 supervisor-review-queuegit 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/supervisor-review-queue)<a href="https://agentmods.dev/skills/zhou210712/claude-for-legal-zh/supervisor-review-queue"><img src="https://agentmods.dev/badge/skills/zhou210712/claude-for-legal-zh/supervisor-review-queue/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/supervisor-review-queue"><img src="https://agentmods.dev/badge/skills/zhou210712/claude-for-legal-zh/supervisor-review-queue.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.00081 | $0.01153 |
| Opus 5.5 | $0.00032 | $0.00461 |
| Sonnet 5.5 | $0.00016 | $0.00231 |
| Haiku 4.5 | $0.00008 | $0.00115 |
Grade A, and why
supervisor-review-queue 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.
This is a copy
86% identical to client-intake — 248 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
/supervisor-review-queue
- 检查
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md→ 指导风格。如果不是"正式审查队列":说明诊所设置为[标记/较轻触],不存在正式队列,以及如何切换。 - 使用以下工作流。
- 默认:按紧急程度、按学生显示等待审查的内容。
- 操作:批准 / 编辑后批准 / 附备注退回。全部记录。
/legal-clinic:supervisor-review-queue
/legal-clinic:supervisor-review-queue --approve Q-003
/legal-clinic:supervisor-review-queue --return Q-004 "检查送达要求——本地规则已变更"
指导老师审查队列(可选)
目的
部分诊所想要一个正式门控:学生起草,指导老师审查,输出发布。其他诊所认为这过于规定性——他们通过案件讨论会和一对一指导,而非通过队列。
本技能仅在 ~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md → 指导风格为"正式审查队列"时活跃。 否则它休眠——冷启动访谈询问指导老师选择哪种模式,这是三个选项之一。
是否使用正式审查工作流对于诊所采纳而言是一个真正的开放问题。它取决于学生经验水平、案件量和指导老师已有的指导方式。指导老师在设置时决定,并可在之后更改。
加载上下文
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md → 指导风格。如果不是"正式审查队列":回应"诊所设置为[标记/较轻触]指导——没有正式队列。[指导老师]通过[诊所现有结构]审查。要切换到正式队列,编辑 CLAUDE.md → 指导风格。"
如果正式队列已启用 → 读取标记触发条件并继续。
队列
保存于 references/review-queue.yaml。每个条目:
- id: Q-001
type: "draft" # intake | draft | memo | status | client-letter
client: "[姓名或编号]"
student: "[姓名]"
submitted: [时间戳]
flags:
- rule: "法院提交"
detail: "驱逐答辩状 — 始终排队"
content_path: "[文件路径]"
status: "pending" # pending | approved | edited-approved | returned
模式
等待审查
## 审查队列 — [日期]
**待审查:** [N]件 | **最久等待:** [N]小时
### 🔴 截止日期敏感
| ID | 类型 | 当事人 | 学生 | 为何标记 | 等待时间 |
|---|---|---|---|---|---|
### 标准
[相同表格]
### 按学生
[分类——发现模式:谁排队很多,谁可能需要关注]
审查某项
展示完整内容 + 为何标记 + 学生备注。
批准 / 编辑后批准 / 退回
- 批准: 状态 → approved,通知学生,记录。
- 编辑后批准: 指导老师内联编辑,批准版本为编辑后的版本,原始记录保留在日志中以便学生查看差异(教学时刻)。
- 退回: 附备注。学生修改并重新提交。
记录
每项操作均有日志。批准日志是诊所记录——它们证明诊所管辖地的持证律师在学生工作发给当事人或法院前进行了审查。这对诊所自身的合规性和学生评估有重要意义。
教学信号
队列也是数据。退回的模式("学生X总是遗漏送达要求")是一个辅导对话。编辑的模式("每个人的律师函都太长")是下学期 /ramp 的更新。
本技能不做什么
- 仅在指导老师选择后才运行。 它是三种指导模式之一,不是唯一。
- 自动批准。 由指导老师批准。
- 替代诊所现有的指导结构。 它是工作成果的门控,不是案件讨论会、一对一或观察学生实际操作的替代。
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 107 lines · 81 tokens per session scan A 58fbf0896f31
supervisor-review-queue 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 81 tokens to every session and 1,153 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to client-intake, differing in 248 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…
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…