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 written-consentgit 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/written-consent)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/written-consent"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/written-consent/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/written-consent"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/written-consent.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.00111 | $0.04652 |
| Opus 5 | $0.00056 | $0.02326 |
| Sonnet 5 | $0.00022 | $0.00930 |
| Haiku 4.5 | $0.00011 | $0.00465 |
Grade A, and why
written-consent 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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/written-consent
- Load
~/.claude/plugins/config/uk-legal-plugins/corporate-legal-uk/CLAUDE.md→ Board & Secretary (resolutions repository, resolution language, company type and nation, board composition). - Use the workflow below.
- Identify the action and classify (routine / review-flag).
- If review-flag: show outside solicitors warning and confirm before proceeding.
- Search resolutions repository for closest precedent. If no repository: use seed resolutions from
~/.claude/plugins/config/uk-legal-plugins/corporate-legal-uk/CLAUDE.md. - Draft resolution in house format using precedent as base.
- Output: resolution draft + signatory checklist + review prompts.
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
Most routine board approvals don't need a meeting. Officer appointments, dividend declarations, bank authorisations, contract approvals above the officer threshold, intercompany arrangements — these happen by written resolution under the Companies Act 2006. This skill drafts them quickly in your house format, finds the prior resolution that's closest to what you need, and flags the actions where you should be getting outside solicitors' eyes before anyone signs.
CA2006 written resolution rules — read before drafting
Private companies (Ltd):
- CA2006 ss.288–300: a private company may pass a resolution in writing without a meeting.
- Ordinary resolution: simple majority of the total voting rights of eligible members.
- Special resolution: not less than 75% of the total voting rights of eligible members.
- A member who would have been disenfranchised at a meeting (e.g., conflict under articles) is still excluded from the written resolution.
- Written copies of the proposed resolution must be sent to every eligible member simultaneously (or as near as reasonably practicable).
- A written resolution lapses if not passed within 28 days (or such longer period as the articles allow) of the circulation date.
- A member must signify agreement to the resolution in writing. Agreement is irrevocable.
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 · 351 lines · 111 tokens per session scan A a871d6609fff
written-consent 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 111 tokens to every session and 4,652 once invoked, about $0.0006 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
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…