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-intakegit 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-intake)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/matter-intake"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/matter-intake/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-intake"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/matter-intake.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.00082 | $0.03604 |
| Opus 5 | $0.00041 | $0.01802 |
| Sonnet 5 | $0.00016 | $0.00721 |
| Haiku 4.5 | $0.00008 | $0.00360 |
Grade A, and why
matter-intake 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 7d 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/matter-intake
- Load
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md→ risk calibration (for triage), landscape (for context, conflicts method), stakeholders (for who to loop in). - Follow the workflow and reference below.
- Run the uniform intake: identification, conflicts check, source, risk triage, materiality, external solicitors, internal owners, legal hold, key dates, initial posture.
- Generate slug from matter name (lowercase, hyphens, year).
- Create
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/matter.md— full narrative intake. - Create
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/history.md— seeded with the intake as the first entry. - Append structured row to
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/_log.yaml. - Confirm with the user: "Here's the row I'll write — any edits?"
Matter Intake
Purpose
Every new matter goes through the same intake so the portfolio stays comparable. Uniform rows in _log.yaml let the status skill roll up. Narrative in matter.md captures what the row can't. History file seeded here becomes the event record.
Load context
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md— risk calibration (triage thresholds, materiality, settlement ladder), landscape (stakeholders, external solicitors bench).~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/_log.yaml— to confirm slug uniqueness.
The intake
1. Identification
- Matter name (as commonly referenced, e.g., "Acme v. Us 2026")
- Counterparty
- Matter type:
contract | employment | ip | regulatory | investigation | product | other - Our role:
claimant | defendant | applicant | respondent | investigated- If the practice profile's
## Sideisclaimant,defendant, or a "both — default X" variant, pre-fill the role from that default and confirm. If## Sideisvaries by matter, ask cold. Never silently assume a posture the practice profile hasn't set. - The role drives downstream skills: claimant-posture matters route risk triage to case value / CFA/DBA economics; defendant-posture matters route to exposure / reserves / insurance tender.
- If the practice profile's
- Jurisdiction (court, arbitration forum, or regulatory body — England & Wales / Scotland / Northern Ireland / other)
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.
- 7d ago First seen · 317 lines · 82 tokens per session scan A 3636d98a15c6
matter-intake 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 82 tokens to every session and 3,604 once invoked, about $0.0004 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.