build-case-chronology

build-case-chronology is a skill for Claude Code, Codex from microsoft/cat-agent-skills. It costs 166 tokens per session (3,060 once invoked), scanned A, original, MIT.

A neutral, source-cited timeline of factual and procedural events assembled from supplied case papers. Each entry points to its document and location and includes flags for dates, evidence, assumptions, discrepancies, and coverage.

In plain words
What is it for?
Use it to prepare a chronology for counsel’s review of a dispute or legal matter. It is for organising facts and procedure, not assessing merits or drafting pleadings.
Why use it?
It turns a large set of case materials into a traceable sequence without mixing in conclusions about liability, the strength of the case, or legal deadlines.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one.

Good fit Use it to prepare a chronology for counsel’s review of a dispute or legal matter. It is for organising facts and procedure, not assessing merits or drafting pleadings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/cat-agent-skills/build-case-chronology
About the project

microsoft/cat-agent-skills is a static website that catalogs reusable instruction sets and related packages for AI agents. People use it to search, filter, rate, and download skills for Cowork, Copilot Studio, and Scout, along with Copilot plugins and Scout automations. The catalogue entries are the skills, instructions, plugins, and settings displayed by the site.

microsoft/cat-agent-skills · 101 stars · on GitHub

Install

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.

Any agent
npx skills add microsoft/cat-agent-skills --skill build-case-chronology
Clone the repo
git clone --depth 1 https://github.com/microsoft/cat-agent-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for build-case-chronology

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/build-case-chronology/github.svg)](https://agentmods.dev/skills/microsoft/cat-agent-skills/build-case-chronology)
Your own site
<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/build-case-chronology"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/build-case-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.

agentmods 80×15 button for build-case-chronology

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/build-case-chronology"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/build-case-chronology.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 166 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,060 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00166 $0.03060
Opus 5.5 $0.00066 $0.01224
Sonnet 5.5 $0.00033 $0.00612
Haiku 4.5 $0.00017 $0.00306

Measured 2d ago against content hash b0bd6c332fd9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

build-case-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 2d 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.

submissions/legal-for-cowork/skills/build-case-chronology/SKILL.md · 231 lines

How it starts

The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Build case chronology

Order supplied case materials into a neutral, fully cited timeline of events, with every entry traceable to a named document and pinpoint. The chronology is a working document for counsel review, not legal advice.

When NOT to Use

  • A view on liability, merits, quantum, limitation or prospects — decline the evaluative part and use legal-reasoning; the chronology itself is still available.
  • Contractual obligations, deadlines and consequences taken from an agreement — use extract-obligations-and-deadlines.
  • Activity across matters drawn from email, Teams and calendar — use summarize-legal-matters.
  • Drafting pleadings, statements, submissions or correspondence — use edit-contract or Cowork's built-in Word document creator.
  • A general summary or explanation of one document — use legal-reasoning or explain-legal-concepts.
  • Disclosure, privilege review or redaction passes — distinct workflows with their own controls.

Hand-off rule. If a request, or part of one, matches an item above that names another skill, do not do that part here — even when the documents are already open and the work looks quick. Name the skill that handles it (for example, "That part is a job for legal-reasoning") and stop that part; finish only what belongs to this skill. If the named skill is not installed, say so plainly and do not attempt it here.

Step 1: Required delivery decision

The output medium defines the deliverable and must not be inferred. If the user already stated one, honor it. Otherwise your first action is a question card, whose first question is Where would you like the output delivered? offering In chat, As a Word document, As an Excel workbook, and Another file format (type it below). Stop and wait; do not read sources or build anything first. Words such as "build", "prepare", "chronology" or "timeline" do not themselves select a medium. If a requested format cannot be produced and validated by an available path, explain and offer the supported ones.

Read the full file on GitHub · 231 lines

Changes

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.

  1. 2d ago First seen · 231 lines · 166 tokens per session scan A b0bd6c332fd9

Subscribe to this mod's changes

build-case-chronology is a skill published in the GitHub repository microsoft/cat-agent-skills (101 stars, last pushed yesterday), licensed MIT. It adds 166 tokens to every session and 3,060 once invoked, about $0.0007 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-11-06.

Related

build-case-chronology compared with skills from other repositories

build-case-chronology next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
build-case-chronologymicrosoft/cat-agent-skillsSkill101yesterdayMITA166Claude Code, Codex
fto-triageanthropics/claude-for-legalSkill9.9kyesterdayApache-2.0A81Claude Code
legal-holdanthropics/claude-for-legalSkill9.9kyesterdayApache-2.0A68Claude Code
specification-writingwanshuiyin/Auto-claude-code-research-in-sleepSkill19ktodayMITA49Claude Code
regulatory-research-fallbackHKUDS/OpenSpaceSkill7.9k2d agoMITA20Claude Code, Codex
terms-of-servicegenspark-ai/genofficeSkill12ktodayApache-2.0A32Claude Code, Codex
x-scorecardx-cmd/x-cmdSkill4.7k8d agoApache-2.0A57Claude Code, Codex