What is matter-briefing?

A briefing workflow that summarises the current position of one legal matter, recent changes, next deadlines, open questions, and risk. It uses the matter record, event history, and portfolio entry.

Use it before a general counsel update or call with external solicitors. It produces a focused briefing and flags matters whose records have not been updated recently.

It removes the need to piece together a matter’s latest position from several files before a meeting or update. It also checks whether the recorded risk and information are still current.

matter-briefing — Skill for Claude Code by uk-agents/uk-legal-plugins

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 matter-briefing

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/matter-briefing/github.svg)](https://agentmods.dev/skills/uk-agents/uk-legal-plugins/matter-briefing)

Your own site

<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/matter-briefing"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/matter-briefing/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/matter-briefing"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/matter-briefing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,313 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.

Model	Per session	Once invoked
Fable 5.1	$0.00072	$0.01313
Opus 5.5	$0.00029	$0.00525
Sonnet 5.5	$0.00014	$0.00263
Haiku 4.5	$0.00007	$0.00131

Measured 1mo ago against content hash 00ebbec7f972, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

matter-briefing 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.

litigation-legal-uk/skills/matter-briefing/SKILL.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/matter-briefing

Load ~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md → risk calibration + relevant stakeholders.
Follow the workflow and reference below.
Read ~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/matter.md + ~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/history.md + log row from _log.yaml.
Produce briefing: current posture, what's changed since last update, next deadline, open questions, risk re-assessment check ("does the risk: field still reflect reality?").
Flag staleness: if last_updated > 30 days, say so.

Matter Briefing

Purpose

Give the counsel a clean read on one matter in the time it takes to walk to a conference room. Current posture, what's changed, what's next, what's worth reconsidering.

Load context

~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/_log.yaml — structured row
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/matter.md — narrative intake
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/history.md — event log
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md — risk calibration (so "risk: high" means something specific, not generic)

Conflicts gate — unbypassable. Before briefing, check _log.yaml for the matter slug. If the matter is not in _log.yaml, refuse and route:

"I don't see [matter slug] in the matter log. Run /litigation-legal-uk:matter-intake first so the conflicts check runs and the matter workspace is set up. I won't build a briefing on a matter that hasn't been intaken — the conflicts check is the gate."

Input

Slug (required). If ambiguous or missing, ask the user to pick from a list of active matters.

The briefing

[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]

# [Matter Name] — Briefing as of [today]

**Status:** [status / stage]
**Risk:** [rating] ([severity] × [likelihood])
**Materiality:** [category]
**External solicitors:** [firm — lead solicitor]
**Last updated:** [date] [flag ⚠️ STALE if >30d]
**Conflicts:** [status — flag ⚠️ if `pending` or `not-run`]

---

## One-paragraph summary

[Current posture. What are we doing and why. Name the pivot fact if one is captured.]

## What's changed recently

[Last 3-5 entries from history.md, most recent first. If history is thin, say so.]

## What's next

- **Immediate CPR deadline:** [next_deadline + what it is + CPR rule basis if known]
- **Upcoming milestones:** [anything dated in matter.md or recent history]
- **Decisions pending:** [open questions flagged in matter.md]
- **Pre-action protocol status:** [if proceedings not yet issued — where are we in the protocol?]

## Exposure

[Range + any change since intake. If reserved, current reserve + whether recalibration is overdue.]

## Internal owners

[Who's looped in; whether anyone should be looped in and isn't]

## Risk re-assessment check

*A prompt, not an answer.*

- Does `risk: [rating]` still feel right, or has the matter moved?
- Does `materiality: [category]` still match? (New facts might push toward reserve or disclosure.)
- Any new stakeholder the matter needs (e.g., CISO becomes relevant after a disclosure development)?
- Has the applicable CPR track or procedural path changed since intake?

## Open questions

[From matter.md and anything unresolved in history]

## For the conversation

[If user specified a purpose — "brief me before the call with external solicitors" — tailor the final section: questions to ask, decisions to get, updates to extract. If no purpose given, omit this section.]

Read the full file on GitHub · 113 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.

1mo ago First seen · 113 lines · 72 tokens per session scan A 00ebbec7f972

Subscribe to this mod's changes

matter-briefing is a skill published in the GitHub repository uk-agents/uk-legal-plugins (14 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,313 once invoked, about $0.0003 per session on Opus 5.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.

Legal and compliance Project management agents-skills claude claude-cowork claude-cowork-plugin claude-marketplace claude-plugin

67-agency-vendor-brief

Dung khi thue NGUOI NGOAI lam — agency, freelancer, production house, vendor: scope of work, spec deliverable, so vong sua, quy trinh duyet, moc thanh toan, dieu khoan IP va bao mat, bang danh gia vendor sau du an. Kich hoat khi user nhac 'brief agency', 'thue freelancer', 'quan ly vendor', 'scope of work', 'agency…

minhnv0807/ai-business-skills · 197 tokens

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

matter-briefing