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 renewal-trackergit 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/renewal-tracker)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/renewal-tracker"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/renewal-tracker/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/renewal-tracker"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/renewal-tracker.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.00102 | $0.02729 |
| Opus 5 | $0.00051 | $0.01365 |
| Sonnet 5 | $0.00020 | $0.00546 |
| Haiku 4.5 | $0.00010 | $0.00273 |
Grade A, and why
renewal-tracker 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.
This is a copy
89% identical to renewal-tracker — 110 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/renewal-tracker
Surfaces what's renewing and when you have to cancel by.
Instructions
-
Read
~/.claude/plugins/config/uk-legal-plugins/commercial-legal-uk/renewal-register.yaml(the config directory — survives plugin updates). -
Default mode: Mode 2 — what's coming up in the next 90 days, grouped by urgency using half-open intervals so each deadline lands in exactly one band: 🔴 0–13 days, 🟠 14–44 days, 🟡 45–89 days. Days 14, 45, and 90 are boundaries — each belongs to exactly one band, not two.
-
--days N: Change the window. -
--missed: Mode 4 — cancel-by deadlines that passed without recorded cancellation. -
If register is empty and the CLM is connected: Offer Mode 3 — scan the CLM for active agreements with renewal dates and bulk-load.
-
Output includes recommended actions: who to ping (the business owner from each register entry), which ones have uncapped pricing (get leverage before window closes), which ones have CPI/RPI escalators.
Examples
/commercial-legal-uk:renewal-tracker
/commercial-legal-uk:renewal-tracker --days 180
/commercial-legal-uk:renewal-tracker --missed
Purpose
Nobody reads a contract twice. The renewal date is extracted once, at review time, and then it lives somewhere — ideally somewhere that shouts at you 45 days before the cancel-by deadline, not 45 days after.
This skill maintains the renewal register and surfaces what's coming.
The register
Lives at ~/.claude/plugins/config/uk-legal-plugins/commercial-legal-uk/renewal-register.yaml (the config directory — survives plugin updates). Each entry:
- counterparty: "Acme SaaS Ltd."
agreement: "Acme Platform Subscription Agreement"
signed_date: 2025-06-15
initial_term_end: 2026-06-15
current_term_end: 2026-06-15 # rolls forward after each auto-renewal; compute cancel_by_* from this
renewal_mechanism: "auto-renew annual"
notice_period_days: 60
notice_method: "email" # email / portal / written notice / registered post / per contract §X
transit_buffer_days: 0 # 0 for email, 2 for first-class post, 5 for registered post
governing_law: "English law" # English law / Scots law / NI law / other
cancel_by_calendar: 2026-04-16 # current_term_end minus notice_period_days
cancel_by_effective: 2026-04-16 # rolled back to last UK business day
send_by_effective: 2026-04-16 # cancel_by_effective minus transit_buffer_days — the date you must SEND the notice
cancel_by_roll_note: "" # e.g., "rolled back from Sunday 2026-11-01; verify against contract's business-day definition"
cancel_by_provenance: "[model calculation — verify against the notice clause]"
price_on_renewal: "then-current list (uncapped)"
annual_value: 48000 # in GBP
currency: "GBP"
business_owner: "[email protected]"
clm_id: "IC-12345" # if connected
docusign_envelope: "abc-123" # if connected
status: "active" # active | cancelled | renewed | lapsed
notes: "Pricing uncapped — revisit before renewal. CPI escalator on renewal."
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.
- 11d ago First seen · 200 lines · 102 tokens per session scan A d59d4a8f95b8
renewal-tracker 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 102 tokens to every session and 2,729 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to renewal-tracker, differing in 110 lines, and is treated as a copy.
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…