legal-hold

legal-hold is a skill for Claude Code from uk-agents/uk-legal-plugins. It costs 68 tokens per session (3,664 once invoked), scanned A, original, Apache-2.0.

A workflow for issuing, refreshing, releasing, or reporting on a legal hold, which tells people to preserve potentially relevant information. It drafts preservation notices and records the hold’s scope, custodians, systems, and review dates.

In plain words
What is it for?
Use it to issue or update a preservation notice, release a hold, or report on holds across matters. It records changes in the portfolio log and schedules the next review.
Why use it?
It helps prevent relevant documents or messages from being deleted during a legal dispute or investigation. It also makes refreshes, releases, and portfolio-wide tracking easier to manage.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md.

Part of the litigation-legal-uk plugin — 16 skills, 1 agent shipped together

Good fit Use it to issue or update a preservation notice, release a hold, or report on holds across matters. It records changes in the portfolio log and schedules the next review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/uk-agents/uk-legal-plugins/legal-hold
Install

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.

Any agent
npx skills add uk-agents/uk-legal-plugins --skill legal-hold
Clone the repo
git clone --depth 1 https://github.com/uk-agents/uk-legal-plugins

Made for: Claude Code.

Or install litigation-legal-uk, the plugin that ships this one along with the rest of its 16 skills, 1 agent.

Wrote 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.

agentmods badge for legal-hold

README.md
[![agentmods](https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/legal-hold/github.svg)](https://agentmods.dev/skills/uk-agents/uk-legal-plugins/legal-hold)
Your own site
<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.

agentmods 80×15 button for legal-hold

Your own site · 80×15
<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>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,664 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash 8b0db2100abf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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.

litigation-legal-uk/skills/legal-hold/SKILL.md · 246 lines

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.

  1. If --status (no slug): read _log.yaml, produce portfolio-wide hold report.
  2. Otherwise: load ~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/matter.md + log row.
  3. Load ~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md → privilege markings, hold template pointer, escalation norms.
  4. Follow the workflow and reference below.
  5. Route by flag:
    • --issue: capture scope, custodians, date range, systems. Draft preservation-notice-v1.docx. Update legal_hold fields. Append history entry. Set next_refresh (default +6mo).
    • --refresh: capture scope/custodian changes. Draft next version. Update last_refresh + next_refresh. Flag departed custodians.
    • --release: capture release date, retention instruction. Draft release notice. Set released: field.
  6. Confirm before writing. Show the user the draft notice and the log diff.

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.

Read the full file on GitHub · 246 lines

Changes

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.

  1. 9d ago First seen · 246 lines · 68 tokens per session scan A 8b0db2100abf

Subscribe to this mod's changes

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.

Related

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.

cbrock84/headcount · 59 tokens

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/.

rsmdt/the-startup · 42 tokens

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.

rsmdt/the-startup · 51 tokens

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…

crevideo/crevideo-reach · 139 tokens

gh-create-issue

Use when filing a GitHub issue for a bug, feature, audit, review finding, or investigated piece of work.

tony/skills · 29 tokens

worktrees

Use when fanning several tickets into parallel branches and git worktrees, with related tickets grouped together.

tony/skills · 23 tokens