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 matter-updategit 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/matter-update)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/matter-update"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/matter-update/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/matter-update"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/matter-update.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.00066 | $0.02063 |
| Opus 5 | $0.00033 | $0.01032 |
| Sonnet 5 | $0.00013 | $0.00413 |
| Haiku 4.5 | $0.00007 | $0.00206 |
Grade A, and why
matter-update 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 8d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/matter-update
- Follow the workflow and reference below.
- Confirm slug exists in
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/and_log.yaml. - Prompt for event type, date (default today), summary, and any log field updates (risk change, status change, next deadline shift, materiality reclassification).
- Append dated entry to
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/history.md. - Update
_log.yaml— setlast_updatedto today, apply any field updates. - Confirm.
Matter Update
Purpose
The portfolio only stays useful if it stays current. This skill makes logging an update cheap — two minutes of structured capture, no freeform drift.
Load context
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/_log.yaml— find the row~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/history.md— append target~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/matter.md— reference (don't rewrite)~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md— risk calibration (if re-assessing risk)
Conflicts gate — unbypassable. Before logging an update, 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-intakefirst so the conflicts check runs and the matter workspace exists. I won't append history to an unmanaged matter — the conflicts check is the gate, and there's nohistory.mdto append to until the matter is intaken."
Input
Slug (required). If not provided, ask — with a short list of recently updated matters to pick from.
The update
1. Event type
Offer categories:
- Procedural — application filed/received, order issued, hearing held, CPR deadline set or confirmed
- Disclosure — disclosure given/received, inspection request, CPR 31.17 third-party disclosure application
- Substantive — new facts, key document surfaced, ruling on merits
- Strategy — posture shift, settlement offer made/received, authority update
- Risk re-assessment — severity or likelihood changed
- Stakeholder — new person looped in, external solicitors change, barrister instructed or changed
- Administrative — engagement letter executed, budget adjusted, hold refreshed, court fee paid
- Pre-action — pre-action protocol steps, letter before action sent/received, protocol compliance completed
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.
- 8d ago First seen · 154 lines · 66 tokens per session scan A ab6a53be3f74
matter-update 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 66 tokens to every session and 2,063 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…
litigation-workflow
Civil litigation workflow expertise — case management, deposition prep, evidence chain, and Federal Rules of Evidence.
gh-create-issue
Use when filing a GitHub issue for a bug, feature, audit, review finding, or investigated piece of work.