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 ThomasMoreAI/legal-skills-open --skill matter-workspacegit clone --depth 1 https://github.com/ThomasMoreAI/legal-skills-openWrote 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/thomasmoreai/legal-skills-open/matter-workspace)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/matter-workspace"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/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/thomasmoreai/legal-skills-open/matter-workspace"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/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.00079 | $0.02471 |
| Opus 5.5 | $0.00032 | $0.00988 |
| Sonnet 5.5 | $0.00016 | $0.00494 |
| Haiku 4.5 | $0.00008 | $0.00247 |
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 24d 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.
This is a copy
86% identical to matter-workspace — 45 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 189 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
/corporate-legal:matter-workspace new <slug>— create a new matter workspace, run a short intake, writematter.md/corporate-legal:matter-workspace list— list matters with status and active flag/corporate-legal:matter-workspace switch <slug>— set the active matter/corporate-legal:matter-workspace close <slug>— archive a matter (move to~/.claude/plugins/config/claude-for-legal/corporate-legal/matters/_archived/, never delete)/corporate-legal:matter-workspace none— detach from any active matter, work at practice-level only
Instructions
- Read
~/.claude/plugins/config/claude-for-legal/corporate-legal/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/corporate-legal: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/claude-for-legal/corporate-legal/matters/<slug>/matter.md, seedhistory.mdandnotes.md.list→ enumerate~/.claude/plugins/config/claude-for-legal/corporate-legal/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/claude-for-legal/corporate-legal/matters/<slug>/to~/.claude/plugins/config/claude-for-legal/corporate-legal/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.
- 24d ago First seen · 189 lines · 79 tokens per session scan A f51904ba1e97
matter-workspace is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (95 stars, last pushed 15d ago), licensed Apache-2.0. It adds 79 tokens to every session and 2,471 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to matter-workspace, differing in 45 lines, and is treated as a copy.
Other skills, from other repositories
evidence-tracker
Manage audit evidence requests, collection progress, and status reporting so Claude can keep audits organized and identify overdue or blocked evidence items.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…