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 claims-chronology-buildergit 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/claims-chronology-builder)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/claims-chronology-builder"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/claims-chronology-builder/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/claims-chronology-builder"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/claims-chronology-builder.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.00035 | $0.01435 |
| Opus 5 | $0.00017 | $0.00718 |
| Sonnet 5 | $0.00007 | $0.00287 |
| Haiku 4.5 | $0.00003 | $0.00144 |
Grade A, and why
Claims Chronology Builder 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 9d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claims Chronology Builder
Purpose
Build a source-cited chronology of an insurance claim — from notices, correspondence, adjuster notes, pleadings, demands, policy documents, medical or property records if provided, and payment history — so a qualified attorney has an organized factual timeline for coverage, claim-handling, or litigation review. This skill organizes dates and events from the documents; it computes no deadline and assesses no claim value.
Use When
- A claim file must be organized into a factual timeline for an attorney.
- Coverage, claim-handling, or bad-faith review needs a sourced chronology of what happened and when.
- A claim spans many documents and a date-ordered, source-cited record is needed before substantive analysis.
Required Inputs
- The claim document set — first notice of loss, claim correspondence, adjuster or examiner notes, pleadings, demands, proofs of loss, and any payment history — with source references.
- The policy or policy documents if available, with source references.
- The policy type (CGL, property, professional, D&O, auto, first-party, third-party, or other) — or
not provided. - The user's role (insurer, insured, claimant, counsel, or other) — or
not provided. - The claim type and the claim stage — or
not provided. - Any dates the user supplies, echoed verbatim and marked
[deadline verification required].
If the claim documents, the policy type, or the user's role is missing, record it as not provided and return the missing-information list first. Build the chronology only from provided documents.
Do Not Use When
- The request is to compute or confirm a deadline, a notice period, a limitations date, or a bar date.
- The request is to value the claim, calculate damages, or set a reserve.
- The request is to conclude on coverage, bad faith, late notice, or claim-handling adequacy.
- The request is for legal advice.
Also out of scope (this skill does not): compute or verify any deadline; assess claim value, damages, or reserves; determine whether notice was timely; conclude on coverage, bad faith, or claim handling; decide what any document legally means; or constitute legal advice.
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.
- 9d ago First seen · 104 lines · 35 tokens per session scan A 1139921b7775
Claims Chronology Builder is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,435 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-09-03.
Other skills, from other repositories
insurance-expert
Expert-level insurance systems, underwriting, claims processing, actuarial analysis, risk assessment, and insurtech solutions. Use when the user mentions underwriting, claims, actuarial, risk, or insurtech, or when the task involves Insurance Systems, Insurance Types, Standards and Regulations, or Claims Processing.
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.
fedramp
Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026). Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document…
eu-cra
Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 — mandatory cybersecurity and vulnerability handling requirements for all products with digital elements (PDEs) sold in the EU. Use this skill for gap analysis, product classification (Default / Class I / Class II), conformity assessment route…