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 zgbrenner/agentcounsel --skill litigation-chronologygit clone --depth 1 https://github.com/zgbrenner/agentcounselWrote 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/zgbrenner/agentcounsel/litigation-chronology)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/litigation-chronology"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/litigation-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/zgbrenner/agentcounsel/litigation-chronology"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/litigation-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.00040 | $0.02888 |
| Opus 5 | $0.00020 | $0.01444 |
| Sonnet 5 | $0.00008 | $0.00578 |
| Haiku 4.5 | $0.00004 | $0.00289 |
Grade A, and why
Litigation 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 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Litigation Chronology
Purpose
Produce a structured, sourced factual chronology of events relevant to a litigation or dispute matter. Every event in the chronology is tied to a specific source document or Bates reference. The skill separates undisputed facts from disputed ones, flags evidentiary gaps, and never resolves or adjudicates a factual conflict. It produces draft legal work product for attorney review — not legal advice and not a statement of what happened.
Use When
- A user asks to "build a timeline," "create a chronology," or "put the facts in order" from a set of documents.
- Counsel needs a fact-organized view of events across multiple documents, productions, or depositions.
- Pre-trial preparation requires organizing the documentary record by event date.
- A mediation brief, motion, or opening statement requires a supporting factual narrative grounded in the record.
- A second attorney is joining the matter and needs a document-grounded orientation to the facts.
- Discovery gaps or missing time periods need to be identified and flagged.
Required Inputs
- One or more source documents (contracts, correspondence, emails, text messages, records, pleadings, deposition excerpts, discovery responses, or other materials). Do not build a chronology without source documents.
- Identification of each source document: document name, Bates range or other identifier, and date of the document if known.
- The matter name or a brief description of the dispute (to give the chronology appropriate context).
- The client's role (plaintiff, defendant, etc.) so that significance assessments can be framed appropriately.
- Privilege posture of the source documents. For each source document (or the set as a whole), confirm one of the following: (a) all documents are cleared for use in this chronology (e.g., produced non-privileged materials); (b) some or all documents may be privileged or of mixed privilege status; or (c) privilege status is unknown. If status is unknown or mixed, do not proceed without attorney confirmation — record
[ATTORNEY TO CONFIRM: privilege status of source documents before distribution of this chronology]and flag the chronology as potentially sensitive.
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.
- 12d ago First seen · 145 lines · 40 tokens per session scan A 692284cffb7a
Litigation Chronology is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 2,888 once invoked, about $0.0002 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
building-chronologies
Use when users say "build a chronology", "make a timeline", "what happened when", "chronology from disclosure", "source the key events", or need legal documents, correspondence, pleadings, witness evidence, or disclosure materials turned into a sourced event chronology.
legaltech-expert
Expert in legal technology: contract lifecycle management, e-discovery, AI-assisted legal research, case and matter management, document automation, and compliance tooling. Use when the user mentions legal case or matter management, e-discovery and legal holds, CLM or contract review and obligation tracking, legal…
investigation-timeline-builder
Builds a structured, annotated chronological timeline from raw notes, documents, or source interview summaries, formatted for both internal reporting use and potential publication as a graphic.
legal-research
A legal research skill for finding and analysing laws and court cases, including similar cases. It requires access to a reliable legal research database before producing a formal report.
document-fill
A document-filling assistant that uses a supplied template and case files to fill in forms, contracts, or legal documents. It also reports where each filled value came from and which details are missing.
contract-review
A contract-review workflow for agreements governed by Chinese law, United States law, or both. It examines clauses one by one and produces a list of legal-risk questions, with an optional marked-up Word document.