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 reg-gap-analysisgit 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/reg-gap-analysis)<a href="https://agentmods.dev/skills/zekaisuni/claude-for-legal-turkish/reg-gap-analysis"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/reg-gap-analysis/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/reg-gap-analysis"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/reg-gap-analysis.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.00095 | $0.03242 |
| Opus 5.5 | $0.00038 | $0.01297 |
| Sonnet 5.5 | $0.00019 | $0.00648 |
| Haiku 4.5 | $0.00010 | $0.00324 |
Grade A, and why
reg-gap-analysis 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
92% identical to reg-gap-analysis — 16 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/reg-gap-analysis
- Read
~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md. Confirm regulatory footprint and use case registry are populated. - Use the framework below.
- Scope: does this regulation apply? (Jurisdiction, threshold, builder/deployer, sector.) If not, one line and done.
- Extract requirements. Diff against current state in
~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md. - Prioritize gaps. Output: remediation plan with must-do / should-do / already compliant / accepted gaps.
- Save as dated markdown doc for the file.
/ai-governance-legal:reg-gap-analysis "EU AI Act (ve Türkiye uyumu) high-risk provisions"
Purpose
The EU AI Act (ve Türkiye uyumu) goes live. Colorado passes an AI law. The CFPB issues model risk guidance. The Rekabet Kurumu / Ticaret Bakanlığı publishes an AI enforcement policy. Something moves — and now you need to know what, if anything, you have to change.
This skill diffs the new requirement against your current AI governance posture
(per ~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md — use case registry, vendor positions, impact assessment practices,
and AI policy commitments) and produces a gap list with a remediation plan.
The AI regulatory landscape is moving faster than any other area of law right now. When a regulation is genuinely ambiguous, say so. Don't paper over uncertainty — legal teams need to know when they're on solid ground versus when they're making a judgment call.
Load current state
Read ~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md:
## Regulatory footprint— what already applies## Use case registry— what AI you're actually running, and under what conditions## AI policy commitments— what you've publicly or contractually committed to## Vendor AI governance— what vendor positions are in place## Impact assessment house style— what assessment practices exist
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 · 242 lines · 95 tokens per session scan A 805e66db6e18
reg-gap-analysis 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 95 tokens to every session and 3,242 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to reg-gap-analysis, differing in 16 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…