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 use-case-triagegit 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/use-case-triage)<a href="https://agentmods.dev/skills/buildwise-studios/claude-for-hk-law/use-case-triage"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/use-case-triage/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/use-case-triage"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/use-case-triage.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.04437 |
| Opus 5.5 | $0.00032 | $0.01775 |
| Sonnet 5.5 | $0.00016 | $0.00887 |
| Haiku 4.5 | $0.00008 | $0.00444 |
Grade A, and why
use-case-triage 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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/use-case-triage
- Read
~/.claude/plugins/config/claude-for-hk-law/ai-governance-legal/CLAUDE.md. Confirm registry is populated — if not, stop and direct to setup. - Use the framework below. Clarify the use case if vague.
- Registry lookup → red line check → classify.
- Output: classification, reasoning, conditions table (if conditional), governance tier, cross-plugin handoffs.
- Propose registry update if use case wasn't already in the registry.
/ai-governance-legal:use-case-triage "Sales team wants to score leads with AI automatically"
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 /ai-governance-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/ai-governance-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
Purpose
Stop the conversation that happens in a hallway and starts as "can we just use AI for this?" Give a fast, calibrated answer from the registry — and if the answer is conditional, make the conditions concrete and the next step obvious.
The triage skill is a gateway, not a destination. Its job is to classify, flag what's required, and route. The aia-generation skill does the deep work.
Read ~/.claude/plugins/config/claude-for-hk-law/ai-governance-legal/CLAUDE.md first
Before triaging, always read ~/.claude/plugins/config/claude-for-hk-law/ai-governance-legal/CLAUDE.md. The use case registry and red lines there
are authoritative. Generic AI ethics reasoning is not a substitute for what this
company has actually decided.
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 · 321 lines · 81 tokens per session scan A 122be8d10583
use-case-triage 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 81 tokens to every session and 4,437 once invoked, about $0.0003 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
c2pa-metadata
Embed C2PA provenance in AI-generated images, video or PDF by script. "add content credentials to this asset".
67-agency-vendor-brief
Dung khi thue NGUOI NGOAI lam — agency, freelancer, production house, vendor: scope of work, spec deliverable, so vong sua, quy trinh duyet, moc thanh toan, dieu khoan IP va bao mat, bang danh gia vendor sau du an. Kich hoat khi user nhac 'brief agency', 'thue freelancer', 'quan ly vendor', 'scope of work', 'agency…
revenue-recognition
Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms…
compensation-and-leveling
Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promotions are decided. Use this to design or revise leveling, set or adjust salary bands, benchmark against market, handle a compensation request or counteroffer, run a review…
employment-compliance
Covers the employment rules that carry real penalties — exempt and non-exempt classification, overtime and hours, employee versus contractor status, work authorization and recordkeeping, accommodation requests, and the notices and retention obligations that go with them. Use this to classify a role, review a…
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.