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 expansion-updategit 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/expansion-update)<a href="https://agentmods.dev/skills/buildwise-studios/claude-for-hk-law/expansion-update"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/expansion-update/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/expansion-update"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/expansion-update.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.00054 | $0.00597 |
| Opus 5 | $0.00027 | $0.00298 |
| Sonnet 5 | $0.00011 | $0.00119 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
expansion-update 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.
This is a copy
89% identical to expansion-update — 4 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/expansion-update
Returns to an open expansion tracker and updates item status based on what has happened since the last session. Recalculates what is now unblocked, flags anything overdue, and surfaces the next priorities.
Instructions
-
Load
~/.claude/plugins/config/claude-for-hk-law/employment-legal/CLAUDE.md. -
Identify the tracker file:
~/.claude/plugins/config/claude-for-hk-law/employment-legal/expansion-[slug].yaml. If it doesn't exist, respond: "No expansion tracker found for [country]. Run/employment-legal:expansion-kickoff [country]to start one." -
Read the tracker. Show the current state:
[Country] Expansion — last updated [date]
Open: [N] | In progress: [N] | Done: [N] | Blocked: [N]
Next priorities (open items with earliest due dates or highest-dependency):
[item] — owner: [owner]
[item] — owner: [owner]
[item] — owner: [owner]
-
Ask for updates in a single prompt — do not ask about each item one by one:
Which items have moved since we last looked? Tell me what's changed (e.g., "EOR decision made — going with Deel", "outside counsel engaged — call scheduled for Thursday", "PE analysis still open, waiting on tax"). You can also add new items or change due dates.
-
Apply updates to the tracker file. For any item newly marked
done, check whether it unblocks other items and flag those as now actionable. -
If any item has a due date that has passed and is still
openorin-progress, flag it:
⚠️ Overdue: [item] — was due [date], owner: [owner]
- Write the updated tracker. Confirm:
Tracker updated — [N] items closed, [N] still open.
Next priority: [top open item].
Examples
/employment-legal:expansion-update Germany
/employment-legal:expansion-update
(will ask which country if multiple trackers exist)
Detailed tracker schema, item-status rules, and dependency logic live in the
international-expansionreference skill — load it before doing substantive work.
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 · 75 lines · 54 tokens per session scan A 744afc8193c9
expansion-update 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 54 tokens to every session and 597 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to expansion-update, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
import-sop
Import agency Standard Operating Procedures — approval workflows, campaign launch checklists, escalation procedures, QA steps — and structure them into numbered, role-assigned steps with human-approval gates marked. SOPs save at the agency level so they apply across every client brand, not per-brand. Triggers on…
chief-operating-officer
Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…
chief-information-officer
The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
chief-content-officer
Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists. Use this to build or fix a content production system, plan a calendar, decide how one piece becomes many, rank content ideas by expected impact, or audit…