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 deal-team-summarygit 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/deal-team-summary)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/deal-team-summary"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/deal-team-summary/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/deal-team-summary"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/deal-team-summary.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.00069 | $0.01219 |
| Opus 5 | $0.00034 | $0.00609 |
| Sonnet 5 | $0.00014 | $0.00244 |
| Haiku 4.5 | $0.00007 | $0.00122 |
Grade A, and why
deal-team-summary 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 12d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deal Team Summary
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
The deal lead doesn't read 200 findings. They read: what's material, what changed since last brief, what needs a decision. This skill compresses the diligence output to the right level for the reader.
Load context
~/.claude/plugins/config/uk-legal-plugins/corporate-legal-uk/CLAUDE.md→ Deal team briefing (cadence, format, what the business reads)~/.claude/plugins/config/uk-legal-plugins/corporate-legal-uk/deals/[code]/deal-context.md→ deal lead, timeline- Current findings from diligence-issue-extraction output
Audience tiers
Per ~/.claude/plugins/config/uk-legal-plugins/corporate-legal-uk/CLAUDE.md — what the business reads vs. what's for the file. Default tiers:
| Audience | Gets | Doesn't get |
|---|---|---|
| Board / exec sponsor | Top 3-5 material issues, price/structure impact, decision items | Category detail, green findings, process |
| Deal lead | All reds, all yellows, progress, decision items, next steps | Green finding detail |
| Working team | Everything — full findings, status by category, gaps | Nothing withheld |
Ask which tier if not obvious.
The summary
Exec tier
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]
> This brief aggregates privileged diligence findings and inherits the sources' legal professional privilege and confidentiality status. Distribution beyond the privilege circle (including to broader business teams) can waive privilege — confirm the distribution list matches the privilege circle before sending.
# [Deal code] — Diligence Brief — [date]
**Status:** [On track / Issues identified / Material findings]
**Coverage:** [X]% of VDR reviewed
## Material findings
[3-5 max. One paragraph each. What it is, why it matters to the deal, what
we're doing about it.]
## Decisions needed
- [ ] [Specific decision — price adjustment, indemnity ask, walk-away trigger]
— [who decides] — [by when]
## Since last brief
[What changed. New findings, findings resolved, coverage progress.]
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.
- 12d ago First seen · 127 lines · 69 tokens per session scan A 9a29e01de64e
deal-team-summary 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 69 tokens to every session and 1,219 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-08-31.
Other skills, from other repositories
m-and-a-strategy
M&A strategy formulation, target screening, synergy modeling, integration planning, and post-merger performance tracking. Use this skill when the user mentions: M&A strategy, mergers and acquisitions, acquisition strategy, buy vs build, target screening, synergy analysis, synergy modeling, integration planning…
pricing-strategy
Design and optimize pricing strategies, analyze willingness-to-pay, build pricing architectures, and model revenue impact. Use this skill when the user mentions: pricing, price strategy, price optimization, willingness to pay, WTP, price elasticity, tiered pricing, freemium, usage-based pricing, price increase…
financial-analysis
Build financial models, perform valuations, analyze cost structures, and develop business cases. Use this skill when the user mentions: financial analysis, financial model, DCF, valuation, P&L, revenue model, cost structure, unit economics, break-even, ROI, NPV, IRR, sensitivity analysis, pro forma, three-statement…
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…
chief-financial-officer
Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls…
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…