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 launch-reviewgit 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/launch-review)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/launch-review"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/launch-review/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/launch-review"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/launch-review.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.00086 | $0.04580 |
| Opus 5 | $0.00043 | $0.02290 |
| Sonnet 5 | $0.00017 | $0.00916 |
| Haiku 4.5 | $0.00009 | $0.00458 |
Grade A, and why
launch-review 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 7d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/launch-review
- Load
~/.claude/plugins/config/uk-legal-plugins/product-legal-uk/CLAUDE.md→ framework + calibration. Stop if placeholders. - Get PRD + related docs. If tracker connected, pull ticket and comments.
- Walk every framework category using the workflow below.
- Calibrate each finding against the table. Novel = flag explicitly.
- Output review memo in house format. Post summary to ticket if connected.
- Hand off: marketing-claims-review if substantial marketing; feature-risk-assessment if a finding needs depth.
/product-legal-uk:launch-review PROJ-1234
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 /product-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/product-legal-uk/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
Destination check
Before producing output, check where it's going. If the user has named a destination (a channel, a distribution list, a counterparty, "everyone"), ask whether it's inside the legal professional privilege circle. Public channels, company-wide lists, counterparty/opposing counsel, vendors, and clients (for legal advice) can break privilege. When the destination looks outside the circle, flag it and offer (a) the privileged version for legal only, (b) a sanitised version for the broader channel, or (c) both.
Purpose
Read the PRD, check every category in this team's framework, calibrate against what actually blocks here (per ~/.claude/plugins/config/uk-legal-plugins/product-legal-uk/CLAUDE.md), and output a review in house format. Goal: a PM reads it and knows exactly what has to happen before they ship — under UK law.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 266 lines · 86 tokens per session scan A a913502d6767
launch-review 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 86 tokens to every session and 4,580 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
performance-management
Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.
specify-meta
Scaffold, status-check, and manage specification directories. Use when creating a new spec, reading spec status, transitioning between phases, or logging decisions on a spec in .start/specs/.
feature-prioritization
RICE, MoSCoW, Kano, and value-effort prioritization frameworks with scoring methodologies and decision documentation. Use when prioritizing features, evaluating competing initiatives, creating roadmaps, or making build vs defer decisions.
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…
litigation-workflow
Civil litigation workflow expertise — case management, deposition prep, evidence chain, and Federal Rules of Evidence.
gh-create-issue
Use when filing a GitHub issue for a bug, feature, audit, review finding, or investigated piece of work.