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 Buildwise-Studios/claude-for-hk-law --skill ai-tool-handoffgit clone --depth 1 https://github.com/Buildwise-Studios/claude-for-hk-lawWrote 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/buildwise-studios/claude-for-hk-law/ai-tool-handoff)<a href="https://agentmods.dev/skills/buildwise-studios/claude-for-hk-law/ai-tool-handoff"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/ai-tool-handoff/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/buildwise-studios/claude-for-hk-law/ai-tool-handoff"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/ai-tool-handoff.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.00102 | $0.01718 |
| Opus 5.5 | $0.00041 | $0.00687 |
| Sonnet 5.5 | $0.00020 | $0.00344 |
| Haiku 4.5 | $0.00010 | $0.00172 |
Grade A, and why
ai-tool-handoff 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Tool Handoff
Matter context
Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /corporate-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-hk-law/corporate-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
Purpose
Luminance and Kira are good at one thing: reading 500 contracts and finding every change-of-control clause. They're less good at judgment — deciding whether a particular CoC provision is actually triggered by this deal structure.
This skill hands off the bulk extraction to the right tool, then runs the QA layer on what comes back.
Before you hand off: try tabular-review first (/corporate-legal:tabular-review). For anything the user's environment can handle — a few hundred documents, a defined column schema — native tabular review is faster to set up, has no per-document cost, and keeps the work product local. Hand off to Luminance/Kira when the corpus is genuinely too large, the team already has a license and workflow, or the matter requires a tool with a validated provenance chain.
Load context
~/.claude/plugins/config/claude-for-hk-law/corporate-legal/CLAUDE.md → AI-assisted review:
- Tool in use (Luminance / Kira / none)
- What it's used for (which clause types)
- Trust level (use as-is / spot-check / full re-review)
- Handoff process (who loads, who QAs)
If ~/.claude/plugins/config/claude-for-hk-law/corporate-legal/CLAUDE.md says no AI tool → this skill is a no-op. Everything goes through diligence-issue-extraction directly.
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 · 134 lines · 102 tokens per session scan A 13c6eeda2ec8
ai-tool-handoff is a skill published in the GitHub repository Buildwise-Studios/claude-for-hk-law (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 102 tokens to every session and 1,718 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
cloud-service-agreement
Draft and fill SaaS agreement templates — cloud contract, MSA, order form, software license, pilot agreement, design partner agreement. Includes variants with SLAs and AI terms. Produces signable DOCX from Common Paper standard forms. Use when user says "SaaS agreement," "cloud contract," "MSA," "order form,"…
data-privacy-agreement
Draft and fill data privacy contract and agreement templates — DPA, data processing contract, GDPR, HIPAA BAA, business associate agreement, AI addendum. Produces signable DOCX files from Common Paper standard forms. Use when user says "DPA," "data processing agreement," "HIPAA BAA," "business associate agreement," or…
kr-patent-full-workflow
A coordinator for writing a Korean patent specification from start to finish. It guides the work through invention interviews, claim preparation, technical details, consistency checks, and final DOCX output.
kr-patent-docx-builder
Nástroj na automatické vytváranie súborov DOCX s textom patentovej prihlášky podľa formulárov Kórejského úradu pre duševné vlastníctvo.
kr-patent-format-unify
A Microsoft Word document-formatting tool for Korean patent specifications. It finds newly added paragraphs and copies the surrounding paragraph and text formatting onto them.
kr-patent-navigation-pane
A tool for adding Word document outline levels to Korean patent specifications without changing their visible formatting.