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 closing-checklistgit 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/closing-checklist)<a href="https://agentmods.dev/skills/zekaisuni/claude-for-legal-turkish/closing-checklist"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/closing-checklist/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/closing-checklist"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/closing-checklist.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.00149 | $0.03612 |
| Opus 5 | $0.00075 | $0.01806 |
| Sonnet 5 | $0.00030 | $0.00722 |
| Haiku 4.5 | $0.00015 | $0.00361 |
Grade A, and why
closing-checklist 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 12d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/closing-checklist
Amaç
Bu skill, Türk M&A ve şirket işlemleri için kapanış checklist'i tutar. Due diligence bulgularından, işlem sözleşmesinden, disclosure schedule'dan ve deal-team notlarından gelen kapanış aksiyonlarını tek listede toplar; neyin kapanışı engellediğini, kimin sorumlu olduğunu ve hangi belgenin kanıt olarak beklendiğini gösterir.
Çıktı bir kapanış sertifikası veya "işlem kapanabilir" hukuki görüşü değildir. Avukat/hukukçu incelemesine tabi çalışma listesidir.
Bağlamı yükle
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.mddosyasını oku.- Varsa
~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/deal-context.mddosyasını oku. - Checklist dosyası varsa oku:
~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/closing-checklist.yaml - Matter workspace açıksa aktif matter
matter.mddosyasını oku; başka matter dosyasına kullanıcı açıkça istemedikçe bakma.
İşlem kodu veya checklist yoksa kısa sor:
- İşlem türü nedir: pay devri, malvarlığı devri, birleşme, bölünme, tür değiştirme, yatırım, JV?
- İmza tarihi ve hedef kapanış tarihi var mı?
- İşlem sözleşmesi veya kapanış listesi taslağı var mı?
- Hangi taraftayız: alıcı, satıcı, hedef şirket, yatırımcı?
Checklist dosyası
Yol:
~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/closing-checklist.yaml
Şema:
deal_code: "[İşlem kodu]"
transaction_type: "[pay devri | malvarlığı devri | birleşme | bölünme | tür değiştirme | yatırım | JV | diğer]"
side: "[alıcı | satıcı | hedef | yatırımcı | grup şirketi]"
signing_date: "[YYYY-MM-DD veya belirsiz]"
target_close: "[YYYY-MM-DD veya belirsiz]"
last_updated: "[YYYY-MM-DD]"
items:
- id: "CP-001"
item: "Rekabet Kurumu izin/bildirim değerlendirmesi"
category: "Regulatory"
phase: "pre-closing"
responsible: "Hukuk / dış danışman"
due: "[YYYY-MM-DD veya belirsiz]"
status: "not_started | in_progress | waiting_counterparty | waiting_authority | complete | waived | post_closing | blocked | unknown"
blocking: true
evidence_required: "Kurul izni/görüşü, başvuru kaydı veya dış danışman notu"
source: "İşlem sözleşmesi m. [ ] / DD bulgusu / kullanıcı sağladı"
notes: ""
- id: "CD-001"
item: "Hedef şirket imza sirküleri ve temsil yetkisi kontrolü"
category: "Corporate"
phase: "signing"
responsible: "Hedef şirket / hukuk"
due: "[YYYY-MM-DD veya belirsiz]"
status: "in_progress"
blocking: true
evidence_required: "Güncel imza sirküleri, iç yönerge veya yetki belgesi"
source: "VDR / Kurumsal kayıtlar"
notes: ""
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.
- 12d ago First seen · 278 lines · 149 tokens per session scan A 158af88955db
closing-checklist is a skill published in the GitHub repository ZekaiSuni/claude-for-legal-turkish (103 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 149 tokens to every session and 3,612 once invoked, about $0.0007 per session on Opus 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-08-30.
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…
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.…
matter-workspace
Manage matter workspaces — new, list, switch, close, or detach (practice-level). File-management logic for keeping one client or engagement's context separate from every other. Use when working across multiple clients or matters, when the user says "new matter", "switch matter", "list matters", "close matter", or when…
patent-docket
A workflow coordinator for patent case files, from an inventor's technical disclosure to patent application documents. A patent docket is the tracked record of a patent matter, including its stage, questions, drafts, and handoffs.
performance-management
Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.