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 customizegit 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/customize)<a href="https://agentmods.dev/skills/buildwise-studios/claude-for-hk-law/customize"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/customize/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/customize"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/customize.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.00089 | $0.01332 |
| Opus 5 | $0.00044 | $0.00666 |
| Sonnet 5 | $0.00018 | $0.00266 |
| Haiku 4.5 | $0.00009 | $0.00133 |
Grade A, and why
customize 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 10d 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
84% identical to customize — 14 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/customize
When this runs
The user typed /ai-governance-legal:customize. They want to change something
in their practice profile — a risk posture, an escalation contact, a playbook
position, a jurisdiction, an output format — without re-running the whole
cold-start interview and without hand-editing YAML.
What to do
-
Read the config. Read
~/.claude/plugins/config/claude-for-hk-law/ai-governance-legal/CLAUDE.md(and~/.claude/plugins/config/claude-for-hk-law/company-profile.mdone level up). If the plugin config does not exist or still contains[PLACEHOLDER]values, say:You haven't run setup yet. Run
/ai-governance-legal:cold-start-interviewfirst — customize is for adjusting a profile you already have. -
Show the customizable map. List what's in the profile, grouped, with a one-line summary of the current value:
- Company / who you are — name, industry, jurisdictions, stage, practice
setting (shared across all 12 plugins — changes flow through
company-profile.md) - Regulatory footprint — PDPO/PCPD, SFC/HKMA sector guidance, cross-border AI rules only if in scope (EU AI Act optional)
- Risk posture — conservative / middle / aggressive, what each means for triage and AIA output
- People — governance team, AI risk owner, escalation chain, approvers
- Use case registry — approved / conditional / never entries, and conditions attached to each
- AI system inventory — per-system role (provider / deployer / etc.) and
risk tier (HK/PDPO-first; EU AI Act if in footprint). Run
/ai-governance-legal:ai-inventoryfor the dedicated editor. - Vendor AI governance — training-on-data, liability, model-change notice, and other positions in your vendor AI playbook
- AI policy commitments — the public or internal commitments your AI policy has made, that the plugin cross-checks against
- Impact assessment house style — AIA section order, risk scoring format, stakeholder framing
- Workflow — intake path, output format, matter workspace paths, review cadence for the policy monitor
- Integrations — what's connected (Slack, document storage, scheduled-tasks), what falls back
- Company / who you are — name, industry, jurisdictions, stage, practice
setting (shared across all 12 plugins — changes flow through
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.
- 10d ago First seen · 115 lines · 89 tokens per session scan A 5ca994c186dc
customize is a skill published in the GitHub repository Buildwise-Studios/claude-for-hk-law (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 89 tokens to every session and 1,332 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to customize, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
c2pa-metadata
Embed a C2PA provenance manifest into an AI-generated marketing asset (PNG, JPG, WebP, GIF, TIFF, MP4, MOV, WebM, MP3, WAV, PDF) via scripts/embed-c2pa.py — produces a signed copy of the file carrying IPTC digital-source-type AI claims, an optional c2pa.ai-disclosure assertion for EU AI Act Article 50 (applicable 2…
privacy-jp
A Japanese-language document generator for services built with Next.js. It creates privacy policies, terms of service, consent dialogs, and cookie banners while considering Japan's personal-information and consumer-protection laws.
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…
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.
contract-review
Reviews and negotiates commercial agreements — MSAs, SOWs, order forms, NDAs, vendor and data-processing agreements — identifying material risk, proposing positions, and recommending a path rather than listing issues. Use this to review a contract before signature, prepare a negotiation position, build fallback…