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 closing-checklistgit 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/closing-checklist)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/closing-checklist"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/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/uk-agents/uk-legal-plugins/closing-checklist"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/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.00103 | $0.03027 |
| Opus 5 | $0.00051 | $0.01514 |
| Sonnet 5 | $0.00021 | $0.00605 |
| Haiku 4.5 | $0.00010 | $0.00303 |
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 11d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/closing-checklist
- Read
~/.claude/plugins/config/uk-legal-plugins/corporate-legal-uk/deals/[code]/closing-checklist.yamland use the modes below. - If status update provided: Mode 3 (update item).
- Otherwise Mode 4: blocking items, critical path, days to completion.
Matter context
Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /corporate-legal-uk:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/uk-legal-plugins/corporate-legal-uk/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
Purpose
Deals complete when the checklist is done. Everything on it, done. Nothing missing. This skill maintains the list, ingests new items as they surface from diligence, and tells the team what's blocking completion ("closing" in UK practice terminology is often called "completion").
The checklist
Lives at ~/.claude/plugins/config/uk-legal-plugins/corporate-legal-uk/deals/[code]/closing-checklist.yaml. Structure:
deal_code: "Project Falcon"
target_completion: [DATE]
exchange_date: [DATE]
last_updated: [DATE]
conditions_precedent:
- id: CP-001
item: "CMA Phase 1 clearance (or expiry of waiting period)"
category: "Regulatory"
responsible: "Buyer's solicitors"
due: 2026-07-15
status: "Notified to CMA 2026-06-01; initial period runs 40 working days"
blocking: true
source: "SPA §7.1(a); Enterprise Act 2002 s.34ZA"
- id: CP-002
item: "FCA Part XII change of control approval — [Target FCA firm]"
category: "Regulatory"
responsible: "Target — [name]"
due: 2026-07-20
status: "Change of control notification submitted 2026-06-10; assessment period 60 working days"
blocking: true
source: "SPA §7.1(b); FSMA 2000 ss.178–191C"
- id: CP-003
item: "Acme Ltd consent to assignment — MSA §14.2"
category: "Third-party consents"
responsible: "Target — [name]"
due: 2026-07-25
status: "Request sent 2026-06-15, no response"
blocking: true
source: "Schedule [X](a)(3); Acme MSA §14.2"
completion_deliverables:
- id: CD-001
item: "Target's certificate of good standing — Companies House"
category: "Corporate"
responsible: "Target's solicitors"
due: 2026-07-28
status: "Not started"
blocking: true
source: "SPA §2.3(b)(iv)"
- id: CD-002
item: "Executed share transfer forms (stock transfer form — J30)"
category: "Corporate"
responsible: "Sellers' solicitors"
due: 2026-07-29
status: "Not started"
blocking: true
source: "SPA §2.3(b)(i)"
# ... etc
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.
- 11d ago First seen · 235 lines · 103 tokens per session scan A 02e968388bfb
closing-checklist 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 103 tokens to every session and 3,027 once invoked, about $0.0005 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-31.
Other skills, from other repositories
pgvector-semantic-search
Use this skill for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search. Trigger when user asks to: Store or search vector embeddings in PostgreSQL Set up semantic search, similarity search, or nearest neighbor search Create HNSW or IVFFlat indexes for vectors…
find-hypertable-candidates
Use this skill to analyze an existing PostgreSQL database and identify which tables should be converted to Timescale/TimescaleDB hypertables. Trigger when user asks to: Analyze database tables for hypertable conversion potential Identify time-series or event tables in an existing schema Evaluate if a table would…
postgres-hybrid-text-search
Use this skill to implement hybrid search combining BM25 keyword search with semantic vector search using Reciprocal Rank Fusion (RRF). Trigger when user asks to: Combine keyword and semantic search Implement hybrid search or multi-modal retrieval Use BM25/pgtextsearch with pgvector together Implement RRF (Reciprocal…
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…
debug
Systematically diagnose and resolve bugs through conversational investigation and root cause analysis.
specify-factory
Decompose a multi-feature or multi-component specification into factory-consumable artifacts. Use this for high-complexity work — multiple features, three or more components, or parallel-eligible workstreams.