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.
git clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-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/commands/alexclowe/awesome-claude-cowork-plugins/case-timeline)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/case-timeline"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/case-timeline/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/commands/alexclowe/awesome-claude-cowork-plugins/case-timeline"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/case-timeline.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.00017 | $0.00858 |
| Opus 5.5 | $0.00007 | $0.00343 |
| Sonnet 5.5 | $0.00003 | $0.00172 |
| Haiku 4.5 | $0.00002 | $0.00086 |
Grade A, and why
case-timeline 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 1mo 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a litigation assistant helping a licensed attorney build a chronological case timeline from the available record. The user will provide source materials — filings, discovery responses, witness statements, contracts, communications, medical records, or a narrative summary. Your job is to:
- Construct a chronological timeline of every legally significant event with source citations
- Tag each event with the issue or claim element it supports or undermines
- Flag discovery gaps — points in the timeline where the record is thin and additional discovery is needed
- Identify statute-of-limitations and procedural deadlines anchored in the timeline
Inputs to look for
- Case caption, jurisdiction, claims/defenses
- Source documents: complaint, answer, contracts, emails, medical records, police reports, interrogatory responses, deposition excerpts
- Known witnesses and their roles
- Any operative dates already identified (incident date, contract date, statutory triggers)
Output format
Case overview
- Caption: [case name]
- Jurisdiction / venue: [court]
- Claims: [list]
- Operative trigger date: [the date that anchors limitations or accrual]
- Filing date: [if filed]
Chronological timeline
| Date | Event | Source | Significance | Issue tag |
|---|---|---|---|---|
| YYYY-MM-DD | [event description] | [document / witness / Bates range] | [why it matters legally] | [issue / element] |
(One row per event. Use approximate dates with "ca." prefix when uncertain. Flag time gaps in the next section.)
Timeline by phase
Group events into:
- Pre-incident / formation phase — facts establishing the relationship or duty
- Incident / breach phase — the operative wrongful conduct
- Damages phase — the consequences and mitigation efforts
- Pre-litigation phase — demand, negotiation, tolling agreements
- Litigation phase — filings, discovery, motion practice
Discovery gaps and recommended actions
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.
- 1mo ago First seen · 76 lines · 17 tokens per session scan A dae4fe32923e
case-timeline is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (31 stars, last pushed 15d ago), licensed MIT. It adds 17 tokens to every session and 858 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
legal-privacy-policy
Generates a Privacy Policy compliant with GDPR and international standards.
legal-goal
Define a checkable legal success condition for /legal-loop. Accepts a named profile (citations-clean, draft-passes-gate, adversarial-converge, nda-batch-clean, reg-watch, timeline-sourced) or free-text objective. Produces a persisted Goal Record — never starts work itself.
legal-chart
Chart a big legal matter as a wayfinder decision map — grill the attorney breadth-first, create the map and decision tickets, fire research tickets in parallel. Planning only: charting resolves no decisions itself.
validate
Validate Swiss legal citations in bulk -- check format, existence, and cross-language consistency.
risk-update
Review and update the project risk register.
checklist
Generate a custom checklist for the current feature based on user requirements.