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 ThomasMoreAI/legal-skills-open --skill 13-hearing-prep-kevinke93git clone --depth 1 https://github.com/ThomasMoreAI/legal-skills-openWrote 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/thomasmoreai/legal-skills-open/13-hearing-prep-kevinke93)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/13-hearing-prep-kevinke93"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/13-hearing-prep-kevinke93/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/thomasmoreai/legal-skills-open/13-hearing-prep-kevinke93"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/13-hearing-prep-kevinke93.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.00054 | $0.01133 |
| Opus 5.5 | $0.00022 | $0.00453 |
| Sonnet 5.5 | $0.00011 | $0.00227 |
| Haiku 4.5 | $0.00005 | $0.00113 |
Grade A, and why
13-hearing-prep-kevinke93 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 26d 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.
What it actually says
Skill：调解、仲裁与庭审准备
事项记忆要求
- 本技能是分析镜头。默认把结果写入会话回复、
matter.md或目标交付文件。 - 只有长期协作、审计追踪或用户明确要求时，才更新
skill_outputs.md。 - 如果本技能没有实际执行，不能在报告中暗示已完成；如果信息不足，输出缺口、影响和下一步。
适用场景
用户即将参加调解、仲裁、法院庭审、行政听证或线上开庭，需要准备发言、质证、发问和应对追问时使用。
目标
- 提炼庭审或听证核心主线。
- 准备简洁陈述。
- 准备证据目录和质证意见。
- 设计对对方的合法发问。
- 预判法官/仲裁员追问。
- 生成或更新案件工作台中的
hearing_playbook.md。 - 避免庭审中自相矛盾或过度情绪化。
输入
- 案件阶段。
- 请求或答辩。
- 证据目录。
- 对方材料。
- 争议焦点和矛盾矩阵。
- 用户担心的问题。
工作流
1. 庭审主线
用三句话说明：
第一句：本案是什么法律关系。
第二句：对方做了什么导致什么后果。
第三句：我方请求什么，证据在哪里。
2. 陈述提纲
结构：
- 法律关系。
- 关键事实时间线。
- 对方违反义务或己方抗辩。
- 损害和金额。
- 证据对应。
- 请求法院/仲裁员支持或驳回的内容。
3. 质证准备
对每份对方证据评价：
- 真实性。
- 合法性。
- 关联性。
- 证明目的是否成立。
- 是否与其他证据矛盾。
4. 发问准备
问题分层：
- 基础事实问题。
- 文件收发问题。
- 行为发生问题。
- 金额/损害问题。
- 矛盾锁定问题。
5. 法官可能追问
准备回答：
- 你的请求依据是什么。
- 金额怎么算。
- 这份证据证明什么。
- 对方这个抗辩你怎么回应。
- 你是否有减损。
- 为什么现在才主张权利。
- 是否愿意调解。
6. 庭审表达风险
- 不与对方争吵。
- 不离开争议焦点讲无关经历。
- 不作无证据的道德指控。
- 不随意承认未核实事实。
- 不隐瞒明显不利事实。
输出格式
## 庭审主线
## 开庭陈述提纲
1.
2.
3.
## 证据使用计划
| 证据 | 证明对象 | 使用时机 | 对方可能质疑 | 回应 |
|---|---|---|---|---|
## 对方证据质证意见
| 对方证据 | 真实性 | 合法性 | 关联性 | 证明目的反驳 |
|---|---|---|---|---|
## 发问清单
| 目标 | 问题 | 预期价值 |
|---|---|---|
## 法官可能追问与回答草稿
| 追问 | 回答要点 | 证据 |
|---|---|---|
案件工作台事项还应同步维护 hearing_playbook.md，至少包含：
- 听证/庭审目标。
- 主线案由或案件理论。
- 举证顺序。
- 质证或反驳重点。
- 对对方的合法发问。
- 裁判者可能追问。
- 风险问题和安全回答原则。
- 开庭前材料清单。
质量检查
- 重点不超过三到五个。
- 每个发问都服务于争议焦点。
- 每份证据都说明证明对象。
- 回答保留不确定性，不随意自认。
- 不设计诱导虚假陈述、威胁、非法取证或骚扰性发问。
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.
- 26d ago First seen · 155 lines · 54 tokens per session scan A 898c99f58f44
13-hearing-prep-kevinke93 is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (95 stars, last pushed 15d ago), licensed Apache-2.0. It adds 54 tokens to every session and 1,133 once invoked, about $0.0002 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-10-02.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…