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 portfoliogit 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/portfolio)<a href="https://agentmods.dev/skills/zekaisuni/claude-for-legal-turkish/portfolio"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/portfolio/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/portfolio"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/portfolio.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.00083 | $0.05572 |
| Opus 5.5 | $0.00033 | $0.02229 |
| Sonnet 5.5 | $0.00017 | $0.01114 |
| Haiku 4.5 | $0.00008 | $0.00557 |
Grade A, and why
portfolio 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 — 530 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/portfolio
Surfaces what's renewing, adds assets, records filings, and audits the register.
Instructions
-
Follow the workflow below and read
~/.claude/plugins/config/claude-for-legal/ip-legal/portfolio.yaml. -
Default (no args): equivalent to
--report— show deadlines in the next 90 days grouped by urgency (🔴 lapsed/grace, ⏰ due within window, 🟡 upcoming, 🌐 agent-managed, ❓ unknown). -
--report [--days N]: Mode 2. Change the window with--days(30 / 60 / 90 / 180 typical). Always prepend the work-product header per CLAUDE.md → Outputs. Always close with the verification caveat. -
--add: Mode 3. Walk through a new asset interactively — type, jurisdiction, number, dates, owner, business owner. Capture a custom rule if the jurisdiction isn't built in. -
--update: Mode 4. Record that a maintenance filing or fee payment was made, sync with the IP management system, or change an asset's status. Enforce the consequential-action gate before setting any deadline tofiled. -
--audit: Mode 5. Broader health check — deadline hygiene, registration gaps, use-in-commerce questions on §8-approaching marks, owner inconsistencies, expiration horizon, unwatched marks. -
If the register is empty and an IP management system is connected: Offer Mode 1 — pull the portfolio from the system of record and initialise the register.
-
Guardrail reminder: Computed deadlines are reference only. Every output closes with a line directing verification against the TÜRKPATENT TSDR, WIPO, or relevant registry before filing or paying. A docketed-but-wrong deadline creates false confidence; do not let the user treat this as the system of record unless the IP management system is sync-integrated.
Examples
/ip-legal:portfolio
/ip-legal:portfolio --report --days 180
/ip-legal:portfolio --add
/ip-legal:portfolio --update
/ip-legal:portfolio --audit
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 · 530 lines · 83 tokens per session scan A aaaf26a2b1fe
portfolio 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 83 tokens to every session and 5,572 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
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.
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…
gap-surfacer
Reference: shared gap- and comment-tracker framework backing /regulatory-legal:gaps and /regulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by…