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-closegit 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-close)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/matter-close"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/matter-close/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-close"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/matter-close.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.00063 | $0.01622 |
| Opus 5 | $0.00032 | $0.00811 |
| Sonnet 5 | $0.00013 | $0.00324 |
| Haiku 4.5 | $0.00006 | $0.00162 |
Grade A, and why
matter-close 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/matter-close
- Follow the workflow and reference below.
- Confirm slug and current status.
- Capture outcome: resolution type (settled, judgment for/against, dismissed/discontinued, withdrawn, consolidated), date, final exposure/cost, lessons.
- Update
_log.yaml:status: closed, addclosed: YYYY-MM-DDandoutcome:fields. - Append final entry to
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/history.md. - Matter stays in
_log.yamland~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/— not deleted./portfolio-statusfilters it from active rollups.
Matter Close
Purpose
Matters end. The outcome is the single most valuable data point the portfolio generates — it calibrates the risk framework for future matters. Closing a matter captures the outcome structurally so the record is useful, not just archived.
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]/matter.md— reference (intake context)~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/history.md— append target
Conflicts gate — unbypassable. Before closing, 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. Nothing to close — either the slug is wrong or the matter was never intaken through
/litigation-legal-uk:matter-intake. Check the slug first; if it genuinely was never intaken, there's no row to update and no file structure to close."
Input
Slug (required).
The close
1. Resolution type
settled— with counterparty, sterling amount, structural terms (Tomlin order / consent order / bare settlement)judgment-for-us— at what stage, appeal exposure (Court of Appeal / UKSC window)judgment-against-us— at what stage, appeal status, exposure crystalliseddiscontinued— claimant discontinued under CPR 38; any costs orderdismissed— dismissed by the court, by what mechanism (strike-out, summary judgment, etc.)withdrawn— by agreement, circumstancesconsolidated— merged into another matter (provide slug of parent matter)other— with explanation
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 · 135 lines · 63 tokens per session scan A 52e4a72b0336
matter-close 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 63 tokens to every session and 1,622 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.