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 LegalQuants/lq-skills --skill building-chronologiesgit clone --depth 1 https://github.com/LegalQuants/lq-skillsWrote 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/legalquants/lq-skills/building-chronologies)<a href="https://agentmods.dev/skills/legalquants/lq-skills/building-chronologies"><img src="https://agentmods.dev/badge/skills/legalquants/lq-skills/building-chronologies/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/legalquants/lq-skills/building-chronologies"><img src="https://agentmods.dev/badge/skills/legalquants/lq-skills/building-chronologies.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.00059 | $0.01533 |
| Opus 5 | $0.00030 | $0.00766 |
| Sonnet 5 | $0.00012 | $0.00307 |
| Haiku 4.5 | $0.00006 | $0.00153 |
Grade A, and why
building-chronologies 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 12d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
building-chronologies
When to Use
- A lawyer needs a timeline from a bundle, disclosure set, correspondence folder, witness statement set, or case file.
- The user asks "what happened when" or needs chronology support for pleadings, advice, witness prep, mediation, or trial.
- The output must cite each event back to a source document.
Do not use this skill to fill gaps from memory. A chronology is only as reliable as its sources.
Audience and Work Shape
Audience: litigators, trainees, paralegals, and litigation-support teams building first-pass chronologies for lawyer review.
Work shape: bounded extraction with accretive judgment. The skill extracts dated events from sources, then applies judgment to de-duplicate, flag conflicts, and surface gaps. It does not decide what happened.
Legal Failure Modes
- Legal support, not legal advice: a chronology is a working evidence map, not merits advice, submissions, or a final statement of facts.
- Privilege/confidentiality: if source material appears privileged or work-product-sensitive, flag it as
privilege_reviewand do not include it in an externally shareable chronology without lawyer approval. - Accountability: the responsible lawyer decides whether a disputed or low-confidence event can be used in pleadings, evidence, settlement material, or submissions.
Access Modes
This skill works in three modes:
- Live source mode - use browser, web search, MCP, API, or other configured access to retrieve public filings, dockets, emails, storage folders, or document repositories.
- User-supplied source mode - use uploaded or pasted documents, correspondence, pleadings, disclosure exports, witness materials, PDFs, images, or OCR text supplied by the user.
- No-source mode - design the chronology schema and source-request list, but do not create factual chronology entries.
If documents cannot be retrieved or supplied, do not infer events from model memory. Mark missing periods, missing sources, and source requests explicitly.
What ships with it
5 files 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.
- 12d ago First seen · 168 lines · 59 tokens per session scan A ebf1aea132ed
building-chronologies is a skill published in the GitHub repository LegalQuants/lq-skills (54 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,533 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-30.
Other skills, from other repositories
Litigation Chronology
Use when building a factual timeline for litigation from provided source documents, producing a structured chronology table with citations, disputed/undisputed flags, and gap analysis for attorney review.
patent-disclosure-skill
A Chinese patent-work assistant for finding invention ideas, writing patent disclosures, explaining patents in plain language, tracking policy changes, and preparing responses to examiner notices.
patent-search
A search tool for published Chinese patent records, using fields such as inventor, applicant, classification number, and title.
patent-docket
A workflow coordinator for patent case files, from an inventor's technical disclosure to patent application documents. A patent docket is the tracked record of a patent matter, including its stage, questions, drafts, and handoffs.
patent-application
A patent-application document workflow that turns supplied invention materials into claims, a description, an abstract, and black-and-white drawings. It can also produce Markdown and Word files.
patent-disclosure
A guided workflow for finding patentable ideas, doing a limited prior-art search, and drafting a Chinese patent disclosure document. A disclosure document describes an invention for later patent drafting.