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 policy-monitorgit 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/policy-monitor)<a href="https://agentmods.dev/skills/zekaisuni/claude-for-legal-turkish/policy-monitor"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/policy-monitor/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/policy-monitor"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/policy-monitor.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.00082 | $0.03390 |
| Opus 5.5 | $0.00033 | $0.01356 |
| Sonnet 5.5 | $0.00016 | $0.00678 |
| Haiku 4.5 | $0.00008 | $0.00339 |
Grade A, and why
policy-monitor 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
100% identical to policy-monitor — 0 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 — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/policy-monitor
Sweep mode (no argument or --sweep):
- Read
~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md→ outputs folder path, AI policy document, last sweep date. - Use the framework below. Scan outputs folder for files since last sweep.
- For each output: extract approved practices → diff against current policy commitments and use case registry.
- Classify gaps: REQUIRED (policy misrepresents current practice) vs ADVISABLE (policy silent).
- For each gap: quote current policy, describe gap, draft suggested language.
- Flag any use cases in outputs not yet added to the
~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.mdregistry. - Present results to the human. Only after acknowledgment, update
Last policy sweepandgaps_foundin~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md.
Direct query mode (with description argument):
- Read
~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md→ current policy commitments, use case registry, actual policy document. - Parse proposed practice. Diff against policy: use case coverage, automation level, affected parties, disclosure, vendor data use, oversight.
- Output: covered / missing / conflicting + suggested language for each gap + registry entry if needed + timing recommendation.
Recurring runs:
Set up a recurring reminder in your own scheduler to run /ai-governance-legal:policy-monitor weekly. Scheduled execution requires a scheduled-tasks integration, which is not bundled with this plugin.
/ai-governance-legal:policy-monitor
/ai-governance-legal:policy-monitor "We want to use AI to automatically flag expense reports for review"
Purpose
AI policies drift from practice faster than almost any other policy document — the field moves quickly, use cases multiply, and each approved AIA or triage result represents a new commitment the policy may not have caught up with. An AIA approves a new AI use case with a human-oversight condition. A vendor AI agreement permits data processing the policy doesn't mention. A triage result marks a new category of deployment as conditional with a disclosure requirement. The policy sits there unchanged.
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 · 355 lines · 82 tokens per session scan A 76c8af655c05
policy-monitor 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 82 tokens to every session and 3,390 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to policy-monitor, differing in 0 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…