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 fto-triagegit 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/fto-triage)<a href="https://agentmods.dev/skills/zekaisuni/claude-for-legal-turkish/fto-triage"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/fto-triage/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/fto-triage"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/fto-triage.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.00081 | $0.06073 |
| Opus 5.5 | $0.00032 | $0.02429 |
| Sonnet 5.5 | $0.00016 | $0.01215 |
| Haiku 4.5 | $0.00008 | $0.00607 |
Grade A, and why
fto-triage 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
95% identical to fto-triage — 18 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 — 538 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fto-triage
This is not a freedom-to-operate opinion. A formal FTO opinion requires a comprehensive search, full claim construction, and element-by-element infringement analysis by registered patent counsel. Patent infringement is strict liability; willful infringement triples damages. A "no obvious blocking patents" result from this skill means the triage didn't find one — it does not mean the product is clear.
Instructions
- Read
~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md. If it contains[PLACEHOLDER], stop and direct to/ip-legal:cold-start-interview. - Follow the workflow below.
- Run intake (product/process, technical detail, jurisdictions, known patents, timing).
- Run a preliminary patent search if a connector is available (Solve Intelligence Patents, or other patent-research MCP). Otherwise say so in the output and proceed with the patents the user has supplied.
- For the 2–5 most plausible patents, build a claim-chart first pass against each independent claim — element by element. Literal read first; flag doctrine-of-equivalents separately; flag indirect / divided infringement.
- List open questions a real FTO study would resolve (enforceability, prosecution history, IPR outcomes, license availability, enforcement history of the assignee).
- Write the triage memo to the matter folder or practice outputs folder. Apply the work-product header per role.
- End with recommended next steps, a willfulness note (knowledge of specific patents factors into willfulness if the company proceeds without further counsel review), and the non-lawyer gate if the role is non-lawyer.
This skill never concludes that a product is clear to launch. If uncertain, flag — patent counsel decides.
Examples
/ip-legal:fto-triage "an on-device speech recognition model for consumer wearables, US launch first"
/ip-legal:fto-triage
THIS IS NOT A FREEDOM-TO-OPERATE OPINION
The loudest guardrail in the plugin. Say this at the top of every output. Do not drop it. Do not soften it. Do not let the reader skim past it.
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 · 538 lines · 81 tokens per session scan A bceadec0b610
fto-triage 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 81 tokens to every session and 6,073 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to fto-triage, differing in 18 lines, and is treated as a copy.
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…