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 ip-clause-reviewgit 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/ip-clause-review)<a href="https://agentmods.dev/skills/zekaisuni/claude-for-legal-turkish/ip-clause-review"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/ip-clause-review/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/ip-clause-review"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/ip-clause-review.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.00067 | $0.04557 |
| Opus 5.5 | $0.00027 | $0.01823 |
| Sonnet 5.5 | $0.00013 | $0.00911 |
| Haiku 4.5 | $0.00007 | $0.00456 |
Grade A, and why
ip-clause-review 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.
How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ip-clause-review
Reviews the IP clauses in an agreement against the practice profile in ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md. Flags assignment gaps, ownership ambiguity, license-scope issues, and IP warranty/indemnity problems. Produces a memo with per-clause findings, prioritized by risk, with suggested redline language where appropriate.
Instructions
-
Load
~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md. If placeholders present, stop and prompt: "Run/ip-legal:cold-start-interviewfirst — I need to learn your practice profile before I can review IP clauses against it." -
Get the agreement: From file path, Drive link, or pasted text. If none provided, ask.
-
Follow the workflow below. In particular:
- Establish the agreement type and which side the company is on for IP (granting / receiving / both). The side question is per-document, not a one-time setup answer.
- Run the assignment gap check first if the agreement is an employment, consulting, SOW, or work-for-hire document.
- Produce per-clause findings prioritized by risk.
- Check cross-clause consistency, not just clause-by-clause.
- Note jurisdiction implications (manevi haklar (FSEK m. 14 vd.) kullanım yetkisi devri, FSEK m.18 / çalışanların eserleri, implied license, patent indemnity).
-
Output the memo per the template below — work-product header first, bottom line, assignment gap check, clauses by severity, consistency flags, jurisdiction note, approval routing.
-
Respect the decision posture. When a clause could be read to allocate IP either way, flag for attorney review and surface the factors cutting both ways. Never silently decide a subjective allocation question.
Examples
/ip-legal:ip-clause-review ~/Documents/vendor-sow.pdf
/ip-legal:ip-clause-review https://docs.google.com/document/d/...
/ip-legal:ip-clause-review
Matter context
Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /ip-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-legal/ip-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
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 · 287 lines · 67 tokens per session scan A 3ce53de83c9d
ip-clause-review 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 67 tokens to every session and 4,557 once invoked, about $0.0003 per session on Opus 5.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
fto-triage
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
terms-of-service
Draft terms of service and a companion privacy notice matched to the product's form and feature modules, not legal advice, delivered as a Word document.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
ai-risk-management
Apply the NIST AI Risk Management Framework (AI RMF 1.0) and adjacent guidance to AI / ML systems — model lifecycle governance, fairness and bias evaluation, robustness, transparency, accountability, third-party model risk, monitoring for drift, and AI incident response. Broader than prompt-injection (which is the…