demand-received

demand-received is a skill for Claude Code from ZekaiSuni/claude-for-legal-turkish. It costs 54 tokens per session (854 once invoked), scanned A, original, Apache-2.0.

A review workflow for an incoming Turkish ihtarname, or formal legal demand notice. It extracts the allegations, legal grounds, requested action, delivery proof, deadlines, related matters, and possible responses.

In plain words
What is it for?
Reviewing demand letters, checking related contracts or parties, assessing the initial merits and risk, and deciding whether to open a matter, draft a response, prepare an intake, or monitor the issue.
Why use it?
It turns a dense notice into a clear list of what happened, what is being demanded, and when action may be needed. It also flags when a deadline cannot be calculated because delivery details are missing.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md.

Part of the litigation-legal plugin — 16 skills, 1 agent shipped together

Good fit Reviewing demand letters, checking related contracts or parties, assessing the initial merits and risk, and deciding whether to open a matter, draft a response, prepare an intake, or monitor the issue.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zekaisuni/claude-for-legal-turkish/demand-received
Install

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.

Any agent
npx skills add ZekaiSuni/claude-for-legal-turkish --skill demand-received
Clone the repo
git clone --depth 1 https://github.com/ZekaiSuni/claude-for-legal-turkish

Made for: Claude Code.

Or install litigation-legal, the plugin that ships this one along with the rest of its 16 skills, 1 agent.

Wrote 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.

agentmods badge for demand-received

README.md
[![agentmods](https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/demand-received/github.svg)](https://agentmods.dev/skills/zekaisuni/claude-for-legal-turkish/demand-received)
Your own site
<a href="https://agentmods.dev/skills/zekaisuni/claude-for-legal-turkish/demand-received"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/demand-received/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.

agentmods 80×15 button for demand-received

Your own site · 80×15
<a href="https://agentmods.dev/skills/zekaisuni/claude-for-legal-turkish/demand-received"><img src="https://agentmods.dev/badge/skills/zekaisuni/claude-for-legal-turkish/demand-received.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 854 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.00854
Opus 5 $0.00027 $0.00427
Sonnet 5 $0.00011 $0.00171
Haiku 4.5 $0.00005 $0.00085

Measured 9d ago against content hash 720082028dad, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

demand-received 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 9d 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.

litigation-legal/skills/demand-received/SKILL.md · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/demand-received

Gelen ihtarnameyi tasnif eder, süre ve riskleri çıkarır, portföy kontrolü yapar, cevap seçenekleri sunar ve gerekiyorsa yeni dosya veya karşı ihtar akışına yönlendirir.

Instructions

  1. Read the provided incoming document.
  2. Load ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml if available for portfolio check.
  3. Load litigation-legal/CLAUDE.md for risk calibration and style.
  4. Extract data, deadlines, allegations, legal bases, and requested action.
  5. Save analysis to ~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/[slug]/analysis.md if writing is appropriate.
  6. Route based on user choice: open matter, draft response, prepare intake, or monitor.

Workflow

Step 1 - Read the Notice

Extract:

  • sender and recipient,
  • representatives,
  • date on document,
  • tebliğ / delivery / KEP timestamp,
  • subject,
  • alleged facts,
  • legal basis,
  • requested action,
  • deadline,
  • attachments,
  • notice method.

If delivery date is missing:

Tebliğ veya teslim tarihi doğrulanmadan kesin son gün hesaplanamaz.

Step 2 - Portfolio Check

Search for related:

  • same counterparty,
  • same contract,
  • same IP/brand/product,
  • same employment/personnel issue,
  • same invoice/payment,
  • same court/UYAP file.

Step 3 - Merits Assessment

Classify:

  • strong,
  • mixed,
  • weak,
  • insufficient information.

Explain evidence and legal basis separately. Do not dismiss a claim solely because tone is aggressive.

Step 4 - Response Options

Options may include:

  • substantive response / objection,
  • counter-notice,
  • cure / payment / performance,
  • negotiation / settlement,
  • request documents,
  • open matter and investigate,
  • no response / monitor, only if legally acceptable.

Step 5 - Deadline Calendar

Record:

deadline:
  trigger_date:
  source: noter | kep | posta | e-posta | other | unknown
  response_deadline:
  confidence: high | medium | low
  note:

Step 6 - Write Analysis

Read the full file on GitHub · 139 lines

Changes

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.

  1. 9d ago First seen · 139 lines · 54 tokens per session scan A 720082028dad

Subscribe to this mod's changes

demand-received 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 54 tokens to every session and 854 once invoked, about $0.0003 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-09-03.

Related

Other skills, from other repositories

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.

wanshuiyin/Auto-claude-code-research-in-sleep · 49 tokens

regulatory-research-fallback

Fallback workflow for regulatory research when web extraction tools fail on government PDFs.

HKUDS/OpenSpace · 20 tokens

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.

x-cmd/x-cmd · 57 tokens

gesellschaftsrechtliche-satzungen-agb

Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.

Klotzkette/claude-fuer-deutsches-recht · 69 tokens

memstack-business-gdpr

Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…

cwinvestments/memstack · 121 tokens

nda-review

Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…

LegalQuants/lq-ai · 79 tokens