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 log-leavegit 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/log-leave)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/log-leave"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/log-leave/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/log-leave"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/log-leave.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.00054 | $0.00701 |
| Opus 5 | $0.00027 | $0.00351 |
| Sonnet 5 | $0.00011 | $0.00140 |
| Haiku 4.5 | $0.00005 | $0.00070 |
Grade A, and why
log-leave 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/log-leave
Adds a new leave entry to ~/.claude/plugins/config/uk-legal-plugins/employment-legal-uk/leave-register.yaml with the minimum
information needed to start tracking deadlines. Use when an employee goes on
leave and you want the tracker to watch the clocks from day one.
Instructions
-
Read
~/.claude/plugins/config/uk-legal-plugins/employment-legal-uk/CLAUDE.md→ jurisdiction table and Systems section. -
Ask all of the following in a single prompt — do not drip them one at a time:
A few quick questions to set up leave tracking:
- Employee name or role (anonymised is fine)
- Where do they work? (E&W / Scotland / NI — this determines which rules apply)
- Leave type: SML (maternity) / SPL (paternity) / SAL (adoption) / ShPL (shared parental) / Parental / Parental Bereavement / long-term sickness
- Leave start date
- Notification date (when did the employer receive the statutory notification?)
- Expected return date (if known — leave blank if not)
- For ShPL: weeks taken from the shared pool; which parent is on leave
- For long-term sickness: has an OH referral been made? Has an adjustments assessment been initiated?
-
Using the jurisdiction table in
~/.claude/plugins/config/uk-legal-plugins/employment-legal-uk/CLAUDE.md, look up the applicable leave entitlement period for this leave type. -
Compute the first upcoming deadline based on the information provided:
- SML/SAL notification received but employer response not sent → deadline is 28 days from notification
- ShPL booking notice received but no employer response → 2-week response window from notice date
- Long-term sickness, no OH referral → flag immediately if absence exceeds 4 weeks
- Both notification and response sent → next deadline is the return date or any change-of-date notice window
-
Write a new entry to
~/.claude/plugins/config/uk-legal-plugins/employment-legal-uk/leave-register.yamlusing the leave register format from the leave-tracker agent. If the file doesn't exist, create it.
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 · 60 lines · 54 tokens per session scan A 9844f74975bd
log-leave 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 54 tokens to every session and 701 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
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…