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 chronologygit 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/chronology)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/chronology"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/chronology/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/chronology"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/chronology.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.00078 | $0.05137 |
| Opus 5 | $0.00039 | $0.02568 |
| Sonnet 5 | $0.00016 | $0.01027 |
| Haiku 4.5 | $0.00008 | $0.00514 |
Grade A, and why
chronology 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 8d 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/chronology
- Load
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/matter.md→ theory, pivot fact, key facts. - Load
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md→ Document storage sources, default matter folder pattern. - Follow the workflow and reference below.
- Identify sources in order: user-provided paths this session, default matter folder, declared sources from
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md. - For readable sources: extract dated events. For unreachable sources: note in Gaps.
- De-dupe, merge with sources list per event.
- Tag significance (🔴/🟡/⚪) per matter theory.
- Write
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/chronology.md(or format variant per flag). - If prior version exists: version number increments, diff summary presented to user.
- Confirm before finalizing: "Here's what I built. Scan the 🔴 entries — anything I miscalled?"
Chronology
Disclosed-document use restrictions
Before working with a set of litigation documents, ask: "Were any of these documents obtained through disclosure in legal proceedings?" If yes:
- England & Wales (CPR 31.22): Documents obtained through disclosure are subject to the implied undertaking — you may only use them for the purpose of the proceedings in which they were disclosed, unless the court grants permission, the disclosing party consents, or the document has been read in open court. Using them for a different matter, a different claim, or a commercial purpose without permission is a contempt.
- Scotland: Equivalent undertaking principles apply under the Rules of the Court of Session and the Sheriff Court Rules. Confirm the applicable position with Scottish solicitors before working with produced documents in a different matter.
- Other jurisdictions: Similar restrictions commonly apply. Check the local rule.
Confirm: "This use is within the proceedings in which the documents were disclosed, or I have permission / consent, or the documents are now public." If not confirmed, flag it: "⚠️ Disclosed documents may have use restrictions. Confirm this use is permitted before proceeding."
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.
- 8d ago First seen · 280 lines · 78 tokens per session scan A 133d835b7889
chronology 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 78 tokens to every session and 5,137 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
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…