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 uk-agents/uk-legal-plugins --skill legal-holdgit clone --depth 1 https://github.com/uk-agents/uk-legal-pluginsWrote 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/uk-agents/uk-legal-plugins/legal-hold)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/legal-hold"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/legal-hold/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/uk-agents/uk-legal-plugins/legal-hold"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/legal-hold.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.00068 | $0.03664 |
| Opus 5 | $0.00034 | $0.01832 |
| Sonnet 5 | $0.00014 | $0.00733 |
| Haiku 4.5 | $0.00007 | $0.00366 |
Grade A, and why
legal-hold 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 9d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/legal-hold
- If
--status(no slug): read_log.yaml, produce portfolio-wide hold report. - Otherwise: load
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/matter.md+ log row. - Load
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md→ privilege markings, hold template pointer, escalation norms. - Follow the workflow and reference below.
- Route by flag:
--issue: capture scope, custodians, date range, systems. Draftpreservation-notice-v1.docx. Updatelegal_holdfields. Append history entry. Setnext_refresh(default +6mo).--refresh: capture scope/custodian changes. Draft next version. Updatelast_refresh+next_refresh. Flag departed custodians.--release: capture release date, retention instruction. Draft release notice. Setreleased:field.
- Confirm before writing. Show the user the draft notice and the log diff.
Legal Hold / Preservation Notice
Purpose
A preservation notice is the most mechanical high-stakes document in-house counsel writes. The notice itself is templated. The failure modes are operational: issued too late, scoped too narrowly, never refreshed, never released. This skill owns all four phases: issue → refresh → (release) → track.
The portfolio already flags missing holds; this skill writes them.
Jurisdiction assumption
Preservation duties under English law derive primarily from common law (the duty to preserve relevant documents once litigation is reasonably anticipated) as well as from the court's procedural powers under CPR Part 31 and CPR Part 51U (extended disclosure in Business and Property Courts). The trigger, scope, and sanctions exposure cited in the draft are a starting-point read for the forum named in the matter:
- England & Wales: duty arises when litigation is reasonably anticipated; scope is documents relevant to the issues in the anticipated litigation; sanctions for breach include adverse inferences, specific disclosure orders, and wasted costs orders.
- Scotland: equivalent obligations under Rules of the Court of Session / Sheriff Court Rules. The trigger and scope are similar to English common law but the procedural framework differs. Flag for Scottish solicitors on any Scotland-domiciled matter.
- Northern Ireland: similar to England & Wales under Rules of the Court of Judicature (NI).
- Regulatory matters: regulatory preservation obligations may overlay civil rules (FCA, ICO, CMA, etc.). Confirm the applicable regime with external solicitors before issuing.
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.
- 9d ago First seen · 246 lines · 68 tokens per session scan A 8b0db2100abf
legal-hold is a skill published in the GitHub repository uk-agents/uk-legal-plugins (9 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 68 tokens to every session and 3,664 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
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.
specify-meta
Scaffold, status-check, and manage specification directories. Use when creating a new spec, reading spec status, transitioning between phases, or logging decisions on a spec in .start/specs/.
feature-prioritization
RICE, MoSCoW, Kano, and value-effort prioritization frameworks with scoring methodologies and decision documentation. Use when prioritizing features, evaluating competing initiatives, creating roadmaps, or making build vs defer decisions.
brand-safety-compliance
Scans outbound copy or creator-submitted content for 6 compliance red lines — medical/efficacy, exaggeration/absolute, beauty-permanence, financial/income, fake-scarcity, fake-rapport — and returns a block/warn verdict with fix suggestions. Use when the user asks to check, scan, review, or vet copy before sending, or…
gh-create-issue
Use when filing a GitHub issue for a bug, feature, audit, review finding, or investigated piece of work.
worktrees
Use when fanning several tickets into parallel branches and git worktrees, with related tickets grouped together.