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 amendment-historygit 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/amendment-history)<a href="https://agentmods.dev/skills/buildwise-studios/claude-for-hk-law/amendment-history"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/amendment-history/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/amendment-history"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/amendment-history.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.00084 | $0.02520 |
| Opus 5.5 | $0.00034 | $0.01008 |
| Sonnet 5.5 | $0.00017 | $0.00504 |
| Haiku 4.5 | $0.00008 | $0.00252 |
Grade A, and why
amendment-history 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.
This is a copy
91% identical to amendment-history — 6 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/amendment-history
Loads a base agreement and all amendments, then either summarizes what changed over time or traces a specific provision to its current controlling language.
Instructions
-
Get the documents: From file upload, [CLM ID (coming soon)], or [repository link (coming soon)]. Accept multiple files in one invocation. If none provided, ask.
-
Detect the mode by parsing the request per the mode detection rules below. If a provision name is clearly stated, go straight to Mode 2. If no provision is mentioned, run Mode 1. Ask only if genuinely ambiguous.
-
Run the workflow below. Follow it fully.
-
Offer follow-ups after output:
- "Want me to trace another provision?"
- "Want a full playbook review of the current agreement as amended?" (routes to vendor-agreement-review)
- "Want a stakeholder summary of the key changes?" (routes to stakeholder-summary)
Examples
/commercial-legal:amendment-history acme-msa.pdf amendment-1.pdf amendment-2.pdf
/commercial-legal:amendment-history --provision indemnity
/commercial-legal:amendment-history
[paste agreement and amendment text]
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
Contracts accumulate amendments. By the third amendment, nobody remembers what the original said or which version of a clause controls. This skill reads the base agreement and all amendments in chronological order and either summarizes what changed across the whole contract or traces a specific provision through every version to find the current controlling language.
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 · 299 lines · 84 tokens per session scan A 0cf13b6e7e2d
amendment-history 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 84 tokens to every session and 2,520 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to amendment-history, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
cloud-service-agreement
Draft and fill SaaS agreement templates — cloud contract, MSA, order form, software license, pilot agreement, design partner agreement. Includes variants with SLAs and AI terms. Produces signable DOCX from Common Paper standard forms. Use when user says "SaaS agreement," "cloud contract," "MSA," "order form,"…
data-privacy-agreement
Draft and fill data privacy contract and agreement templates — DPA, data processing contract, GDPR, HIPAA BAA, business associate agreement, AI addendum. Produces signable DOCX files from Common Paper standard forms. Use when user says "DPA," "data processing agreement," "HIPAA BAA," "business associate agreement," or…
kr-patent-full-workflow
A coordinator for writing a Korean patent specification from start to finish. It guides the work through invention interviews, claim preparation, technical details, consistency checks, and final DOCX output.
kr-patent-docx-builder
Nástroj na automatické vytváranie súborov DOCX s textom patentovej prihlášky podľa formulárov Kórejského úradu pre duševné vlastníctvo.
kr-patent-format-unify
A Microsoft Word document-formatting tool for Korean patent specifications. It finds newly added paragraphs and copies the surrounding paragraph and text formatting onto them.
kr-patent-navigation-pane
A tool for adding Word document outline levels to Korean patent specifications without changing their visible formatting.