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 escalation-flaggergit 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/escalation-flagger)<a href="https://agentmods.dev/skills/buildwise-studios/claude-for-hk-law/escalation-flagger"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/escalation-flagger/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/escalation-flagger"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/escalation-flagger.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.00096 | $0.02066 |
| Opus 5 | $0.00048 | $0.01033 |
| Sonnet 5 | $0.00019 | $0.00413 |
| Haiku 4.5 | $0.00010 | $0.00207 |
Grade A, and why
escalation-flagger 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 12d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/escalation-flagger
Names the approver for a contract issue per the ~/.claude/plugins/config/claude-for-hk-law/commercial-legal/CLAUDE.md escalation matrix and drafts the message so you're not writing "hey got a sec" at 5pm.
Instructions
-
Load
~/.claude/plugins/config/claude-for-hk-law/commercial-legal/CLAUDE.md→ Escalation section. If missing, say so — the practice profile needs editing. -
Characterize the issue: dollar threshold / term deviation / automatic trigger / business decision.
-
Match to matrix, name the approver. Be specific — a person or role, not "legal leadership."
-
Draft the ask per the template below: what the contract says, what playbook says, options with recommendation, decision-by date.
-
Do not send. Draft it, show it, let the lawyer send.
Examples
/commercial-legal:escalation-flagger
The Acme MSA has uncapped liability — who approves and what do I say?
/commercial-legal:escalation-flagger
Reference: acme-review-memo.md
Issue: §8.2 indemnity carveouts
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 /commercial-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/commercial-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
Purpose
Every contracts team has an escalation matrix, written or not. This skill reads the written one (in ~/.claude/plugins/config/claude-for-hk-law/commercial-legal/CLAUDE.md), matches a contract issue against it, names the approver, and drafts the ask so the lawyer isn't writing "hey do you have a sec" messages at 5pm.
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.
- 12d ago First seen · 160 lines · 96 tokens per session scan A 6642f9f8a6db
escalation-flagger 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 96 tokens to every session and 2,066 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…
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…
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…