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 contract-drafting-and-review-guidance-china-lawgit 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/contract-drafting-and-review-guidance-china-law)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/contract-drafting-and-review-guidance-china-law"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/contract-drafting-and-review-guidance-china-law/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/contract-drafting-and-review-guidance-china-law"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/contract-drafting-and-review-guidance-china-law.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.00036 | $0.03965 |
| Opus 5.5 | $0.00014 | $0.01586 |
| Sonnet 5.5 | $0.00007 | $0.00793 |
| Haiku 4.5 | $0.00004 | $0.00396 |
Grade A, and why
contract-drafting-and-review-guidance-china-law 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
94% identical to contract-drafting-and-review-guidance-china-law — 10 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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This skill applies the Chinese contract drafting and review method known as "三观四步法" from 合同起草审查指南 (T/CAB 0121-2021). It helps lawyers, in-house counsel, business operators, and legal students structure contract review, draft contract frameworks, identify risks, and produce review comments under a China-law lens.
This skill is a workflow and checklist tool. It does not replace current legal research or advice from a licensed lawyer.
When to Use This Skill
- The user asks to review a contract, draft a contract, or identify contract risks.
- The user asks how to structure a transaction before drafting documents.
- The user asks whether a contract form, clause order, or clause wording is appropriate.
- The user asks for a checklist for contract parties, subject matter, procedures, performance, breach, dispute resolution, or signing requirements.
- The contract is governed by PRC law or the user asks for China-law contract drafting logic.
HOW TO USE THIS SKILL
- Identify the user's task: contract review, contract drafting, deal-structure design, clause rewrite, or checklist generation.
- Ask only for missing facts that are necessary: contract type, user role, transaction purpose, counterparty identity, subject matter, price/payment, timeline, and special risk tolerance.
- Apply the four-step process: communicate needs -> analyze through three perspectives -> review -> submit.
- Analyze in this order: macro transaction structure -> meso contract structure -> micro clause wording.
- If legal validity depends on current statutes, regulatory approvals, judicial interpretations, or local rules, tell the user to verify current law or consult qualified counsel.
CITATION RULES
Every substantive claim based on the guide's methodology must include a citation to the original text.
Quote files (load the relevant one):
contract-drafting-quotes.md: definitions of macro, meso, micro analysis; drafting principles; transaction structure; parties; three-points-one-line method.contract-review-quotes.md: the complete 三观四步法 statement, review principles, transaction-structure framing, and comprehensive review.
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 · 361 lines · 36 tokens per session scan A b482b15fb1f4
contract-drafting-and-review-guidance-china-law is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (95 stars, last pushed 14d ago), licensed Apache-2.0. It adds 36 tokens to every session and 3,965 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to contract-drafting-and-review-guidance-china-law, differing in 10 lines, and is treated as a copy.
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…