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-closegit 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-close)<a href="https://agentmods.dev/skills/zekaisuni/claude-for-legal-turkish/matter-close"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/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/zekaisuni/claude-for-legal-turkish/matter-close"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/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.01455 |
| Opus 5.5 | $0.00025 | $0.00582 |
| Sonnet 5.5 | $0.00013 | $0.00291 |
| Haiku 4.5 | $0.00006 | $0.00145 |
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 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-close — 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 — 131 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, dismissed, judgment for/against, withdrawn, consolidated), date, final exposure/cost, lessons.
- Update
_log.yaml:status: closed, addclosed: YYYY-MM-DDandoutcome:fields. - Append final entry to
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md. - Matter stays in
_log.yamland~/.claude/plugins/config/claude-for-legal/litigation-legal/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/claude-for-legal/litigation-legal/matters/_log.yaml— find the row~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md— reference (intake context)~/.claude/plugins/config/claude-for-legal/litigation-legal/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: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, dollar amount, structural termsdismissed— with or without prejudice, by what mechanismjudgment-for-us— at what stage, appeal exposurejudgment-against-us— at what stage, appeal status, exposure crystallizedwithdrawn— by counterparty, circumstancesconsolidated— merged into another matter (provide slug of parent)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.
- 1mo ago First seen · 131 lines · 63 tokens per session scan A 545801921f2c
matter-close 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 63 tokens to every session and 1,455 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-close, 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…