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-workspacegit 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-workspace)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/matter-workspace"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/matter-workspace/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-workspace"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/matter-workspace.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.02292 |
| Opus 5 | $0.00041 | $0.01146 |
| Sonnet 5 | $0.00016 | $0.00458 |
| Haiku 4.5 | $0.00008 | $0.00229 |
Grade A, and why
matter-workspace 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 11d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/matter-workspace
Practitioners work across multiple clients and matters. A matter workspace keeps one client or engagement's context separate from every other. This skill manages those workspaces.
Subcommands
/ai-governance-legal-uk:matter-workspace new <slug>— create a new matter workspace, run a short intake, writematter.md/ai-governance-legal-uk:matter-workspace list— list matters with status and active flag/ai-governance-legal-uk:matter-workspace switch <slug>— set the active matter/ai-governance-legal-uk:matter-workspace close <slug>— archive a matter (move to~/.claude/plugins/config/uk-legal-plugins/ai-governance-legal-uk/matters/_archived/, never delete)/ai-governance-legal-uk:matter-workspace none— detach from any active matter, work at practice-level only
Instructions
- Read
~/.claude/plugins/config/uk-legal-plugins/ai-governance-legal-uk/CLAUDE.md— confirm the## Matter workspacessection is populated. IfEnabledis✗, tell the user: "Matter workspaces are off — you're configured as an in-house practice with one client, so the plugin works from practice-level context automatically. If you actually work across multiple clients, re-run/ai-governance-legal-uk:cold-start-interview --redoand select a private-practice setting. Otherwise, you don't need/matter-workspaceat all." Don't error — the disabled state is the expected one for in-house users. - Use the workflow below.
- Dispatch on the first token of
$ARGUMENTS:new→ run the intake interview, write~/.claude/plugins/config/uk-legal-plugins/ai-governance-legal-uk/matters/<slug>/matter.md, seedhistory.mdandnotes.md.list→ enumerate~/.claude/plugins/config/uk-legal-plugins/ai-governance-legal-uk/matters/*/matter.md, print a table, mark the active matter.switch→ update theActive matter:line in the practice-level CLAUDE.md.close→ move~/.claude/plugins/config/uk-legal-plugins/ai-governance-legal-uk/matters/<slug>/to~/.claude/plugins/config/uk-legal-plugins/ai-governance-legal-uk/matters/_archived/<slug>/, log the close date inhistory.md.none→ setActive matter:tonone — practice-level context only.
- Show the user what changed and confirm before writing.
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.
- 11d ago First seen · 184 lines · 82 tokens per session scan A 07e99491e302
matter-workspace 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 2,292 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-08-31.
Other skills, from other repositories
todos
Own the To-Do Protocol - user tasks in vault tasks.md files, optional Notion Kanban mirror, status reporting. Actions - new (create a task, user confirmation required), sync, push, pull, board (Notion mode only), status, overview. Fully functional without Notion (vault-only mode).
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
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.
reply-triage
A sorting guide for creator replies, emails, and automation results. It puts incoming items into five priority groups and suggests what to do next.
gh-create-issue
Use when filing a GitHub issue for a bug, feature, audit, review finding, or investigated piece of work.