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 ZekaiSuni/claude-for-legal-turkish --skill matter-workspacegit clone --depth 1 https://github.com/ZekaiSuni/claude-for-legal-turkishWrote 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/zekaisuni/claude-for-legal-turkish/matter-workspace)<a href="https://agentmods.dev/skills/zekaisuni/claude-for-legal-turkish/matter-workspace"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/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/zekaisuni/claude-for-legal-turkish/matter-workspace"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/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.02448 |
| Opus 5.5 | $0.00033 | $0.00979 |
| Sonnet 5.5 | $0.00016 | $0.00490 |
| Haiku 4.5 | $0.00008 | $0.00245 |
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 1mo 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
100% identical to matter-workspace — 0 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 — 186 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:matter-workspace new <slug>— create a new matter workspace, run a short intake, writematter.md/ai-governance-legal:matter-workspace list— list matters with status and active flag/ai-governance-legal:matter-workspace switch <slug>— set the active matter/ai-governance-legal:matter-workspace close <slug>— archive a matter (move to~/.claude/plugins/config/claude-for-legal/ai-governance-legal/matters/_archived/, never delete)/ai-governance-legal:matter-workspace none— detach from any active matter, work at practice-level only
Instructions
- Read
~/.claude/plugins/config/claude-for-legal/ai-governance-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/ai-governance-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/ai-governance-legal/matters/<slug>/matter.md, seedhistory.mdandnotes.md.list→ enumerate~/.claude/plugins/config/claude-for-legal/ai-governance-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/ai-governance-legal/matters/<slug>/to~/.claude/plugins/config/claude-for-legal/ai-governance-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.
- 1mo ago First seen · 186 lines · 82 tokens per session scan A 8226cf1c7d54
matter-workspace is a skill published in the GitHub repository ZekaiSuni/claude-for-legal-turkish (108 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 82 tokens to every session and 2,448 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to matter-workspace, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
vendor-review
Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.
integration-management
Post-closing M&A integration tracker — phased workplan, consent tracking, contract assignment at scale, weekly status reports. Initializes from whatever deal artifacts are available (purchase agreement, deal summary, closing checklist) and connects to deal-context.md and closing-checklist.yaml from the M&A cold-start.…
entity-compliance
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity…
portfolio
Track the IP portfolio — registrations, renewals, maintenance fees, and use declarations. Use when checking what's renewing, adding or updating an asset, recording a maintenance filing, or auditing the register for gaps, lapses, and use-in-commerce questions. Receives handoffs from prosecution and clearance work.
launch-review
Full launch review against your framework and risk calibration. Use when the user says "review this launch", "legal review for [feature]", "can we ship this", "what are the legal issues with [product]", or references a launch tracker ticket or PRD that needs a category-by-category review memo.
client-intake
Structured intake — practice-area templates, cross-area issue spotting, conflict flags, and triage classification. Produces a formatted case summary the student analyzes and the professor reviews. Does NOT decide case acceptance. Use when starting a new client intake, running an intake interview, or writing up a new…