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 uk-agents/uk-legal-plugins --skill demand-receivedgit clone --depth 1 https://github.com/uk-agents/uk-legal-pluginsWrote 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/uk-agents/uk-legal-plugins/demand-received)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/demand-received"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/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.
<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/demand-received"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/demand-received.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.00078 | $0.03174 |
| Opus 5 | $0.00039 | $0.01587 |
| Sonnet 5 | $0.00016 | $0.00635 |
| Haiku 4.5 | $0.00008 | $0.00317 |
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 8d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/demand-received
- Read the incoming document from provided path.
- Load
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/_log.yamlfor portfolio cross-check. - Load
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md→ risk calibration, landscape, Letter Before Action practice. - Follow the workflow and reference below.
- Extract fields; cross-check portfolio; assess merit; present options with recommendation.
- Write
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/inbound/[slug]/triage.md. Copy or link incoming to~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/inbound/[slug]/incoming.[ext]. - Hand off per user choice:
- Create matter →
matter-intakepre-populated - Respond with counter-demand →
demand-intakepre-populated - Link to existing matter → update
related_mattersin log - Standalone → no further action
- Create matter →
Demand Received
Purpose
Inbound Letters Before Action and Letters of Claim are the bread and butter of an in-house litigation practice. A small fraction need escalation; most can be handled with a structured response or a holding letter. The failure mode is treating them all alike. This skill triages, cross-checks the portfolio, and produces options.
Load context
- The incoming document (user provides path or drops it in-session)
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/_log.yaml— scan for related matters (same counterparty, overlapping counterparties via entity relationships, or matter type + recent date)~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md→ risk calibration (for merit assessment), landscape (is the sender a frequent adversary?), Letter Before Action practice (house tone and response defaults)
Workflow
Step 1: Read the demand
Extract from the incoming:
- Sender — entity, signer, solicitors (if signed by external firm)
- Recipient — which entity/person at our company
- Delivery — recorded post, email, courier (matters for limitation and pre-action protocol timeline calculation)
- Date received vs. date signed
- Demand type — payment, breach/cure, C&D, preservation, settlement, other
- Specific asks — what they want, by when
- Facts alleged — their version of what happened
- Legal basis — statutes, contract provisions, theories they cite (OSCOLA-tag each for verification)
- Threats — what they say they'll do if we don't comply (issue proceedings, seek injunction, etc.)
- Settlement-communication framing — is this marked "without prejudice" or "without prejudice save as to costs"? Note whether it is marked as such, but remember: protection attaches from conduct and context, not merely from labelling. Capture both the label (if any) and a first-pass read of whether the substance is in fact a compromise discussion.
- Applicable CPR pre-action protocol — does the demand purport to comply with a specific pre-action protocol? Note which one. Non-compliance with a protocol by either party can affect costs later.
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.
- 8d ago First seen · 241 lines · 78 tokens per session scan A 0f17fd26a84a
demand-received is a skill published in the GitHub repository uk-agents/uk-legal-plugins (9 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 78 tokens to every session and 3,174 once invoked, about $0.0004 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.
Other skills, from other repositories
brand-safety-compliance
Scans outbound copy or creator-submitted content for 6 compliance red lines — medical/efficacy, exaggeration/absolute, beauty-permanence, financial/income, fake-scarcity, fake-rapport — and returns a block/warn verdict with fix suggestions. Use when the user asks to check, scan, review, or vet copy before sending, or…
postgres
Use this skill for any PostgreSQL database work — table design, indexing, data types, constraints, extensions (pgvector, PostGIS, TimescaleDB), search, and migrations. Trigger when user asks to: Design or modify PostgreSQL tables, schemas, or data models Choose data types, constraints, indexes, or partitioning…
revenue-recognition
Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms…
privacy-and-data-protection
Assesses and improves how personal data is collected, used, shared, and retained — data mapping, lawful basis, consent, processor agreements, subject rights, and breach obligations. Use this before launching anything that handles personal data, when adding a vendor that will process it, when a data subject request…
benefits-and-leave
Designs and runs employee benefits and leave — health and retirement plans, leave policy, cost and renewal, and the administration that keeps them compliant. Use this to design or review a benefits package, prepare for a renewal, write leave policy, handle a leave request, or decide what benefits are worth their cost.
compensation-and-leveling
Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promotions are decided. Use this to design or revise leveling, set or adjust salary bands, benchmark against market, handle a compensation request or counteroffer, run a review…