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 entity-compliancegit 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/entity-compliance)<a href="https://agentmods.dev/skills/buildwise-studios/claude-for-hk-law/entity-compliance"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/entity-compliance/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/entity-compliance"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/entity-compliance.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.00098 | $0.05031 |
| Opus 5 | $0.00049 | $0.02516 |
| Sonnet 5 | $0.00020 | $0.01006 |
| Haiku 4.5 | $0.00010 | $0.00503 |
Grade A, and why
entity-compliance 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 11d 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 — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/entity-compliance
- Load
~/.claude/plugins/config/claude-for-hk-law/corporate-legal/CLAUDE.md→## Entity Management(entity table, jurisdictions, company secretarial provider). - Route to the correct mode below based on flag:
- No flag or
--init: Mode 1 — initialize tracker from entity table --report: Mode 2 — surface upcoming deadlines and overdue items--update: Mode 3a (manual) or 3b (--from-report upload) — update status--sweep: Mode 3c — walk through unknown/overdue items one by one--audit: Mode 4 — full health audit--export: Mode 5 — produce CSV or table export
- No flag or
- Read/write
~/.claude/plugins/config/claude-for-hk-law/corporate-legal/entities/compliance-tracker.yaml. - After any update: show summary of changes and next action.
Purpose
Annual returns, financial statements, directors' reports, and significant controllers registers — every HK company and every foreign jurisdiction has its own filing schedule under the Companies Ordinance (Cap 622) and its own consequences for missing the deadline. This skill maintains a single YAML tracker that knows what's due, when, and for which entity. It's lightweight by design: the tracker is a file you own, Claude updates it on command, and you export it when you need to share it.
Important: deadline reference caveat
The filing deadlines in this skill's reference table reflect publicly available requirements as of the skill's build date. HK filing requirements and due dates can change via legislative amendments. Always confirm deadlines with the Companies Registry (HK) or directly with the relevant registry before relying on them for compliance purposes. If you use a corporate services provider, their compliance calendar is authoritative for your specific entities — use this tracker to organize and surface their data, not to replace it.
Jurisdiction assumption
This tracker computes deadlines against the jurisdiction of formation / registration recorded per entity. Filing rules, due-date mechanics, and fee structures vary materially by jurisdiction. If an entity's actual footprint differs from what's in
~/.claude/plugins/config/claude-for-hk-law/corporate-legal/CLAUDE.md(undisclosed foreign registration, dissolved entities, jurisdictional changes, international filings managed by a local agent), the output may not apply as written — confirm with the corporate services provider or local counsel for that jurisdiction.
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.
- 11d ago First seen · 449 lines · 98 tokens per session scan A ee7b05e7aa99
entity-compliance 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 98 tokens to every session and 5,031 once invoked, about $0.0005 per session on Opus 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 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…
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…
privacy-and-data-protection
Assesses and improves how personal data is collected, used, shared, and retained — data mapping, lawful basis, consent, processor agreements, subject rights, and breach obligations. Use this before launching anything that handles personal data, when adding a vendor that will process it, when a data subject request…
benefits-and-leave
Designs and runs employee benefits and leave — health and retirement plans, leave policy, cost and renewal, and the administration that keeps them compliant. Use this to design or review a benefits package, prepare for a renewal, write leave policy, handle a leave request, or decide what benefits are worth their cost.