claims-doc

claims-doc is a command for Claude Code from alexclowe/awesome-claude-cowork-plugins. It costs 10 tokens per session (773 once invoked), scanned A, original, MIT.

A structured document generator for insurance claims, including the incident, people involved, damage or injury, and an analysis of relevant policy coverage.

In plain words
What is it for?
Use it to document auto accidents, property damage, theft, liability claims, and other losses, then prepare client-facing explanations.
Why use it?
It helps agents organize facts and explain which parts of a policy may apply, giving the claims process a clearer record.

Command for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the insurance-agent plugin — 2 skills, 4 commands shipped together

Good fit Use it to document auto accidents, property damage, theft, liability claims, and other losses, then prepare client-facing explanations.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/alexclowe/awesome-claude-cowork-plugins/claims-doc
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.

Clone the repo
git clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-plugins

Made for: Claude Code.

Or install insurance-agent, the plugin that ships this one along with the rest of its 2 skills, 4 commands.

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 claims-doc

README.md
[![agentmods](https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/claims-doc/github.svg)](https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/claims-doc)
Your own site
<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/claims-doc"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/claims-doc/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 claims-doc

Your own site · 80×15
<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/claims-doc"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/claims-doc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 773 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.00010 $0.00773
Opus 5.5 $0.00004 $0.00309
Sonnet 5.5 $0.00002 $0.00155
Haiku 4.5 $0.00001 $0.00077

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

Security

Grade A, and why

claims-doc 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 23d 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.

insurance-agent/commands/claims-doc.md · 91 lines

How it starts

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

You are an insurance documentation assistant helping an agent prepare structured claims documentation.

The user will provide details about an incident and the client's policy information. Your job is to create organized, thorough documentation that supports the claims process and keeps the client informed.

Output format

Structure the documentation in these sections:

Incident Summary

  • Date of Incident: [Date]
  • Date Reported: [Date or "today"]
  • Policy Number: [Placeholder for agent to add]
  • Insured: [Client name]
  • Type of Loss: [Category — auto accident, property damage, theft, liability claim, etc.]
  • Description: Clear, factual narrative of what happened — 2–3 paragraphs covering:
    • What occurred (sequence of events)
    • Who was involved (parties, witnesses)
    • Where it happened
    • Extent of damage or injury (as known)
    • Immediate actions taken

Applicable Coverage Analysis

For each relevant coverage area:

Coverage Applies? Limit Deductible Notes
(coverage areas based on policy type)

Then provide a narrative explanation:

  • Which coverages apply to this incident and why
  • Which coverages do NOT apply (and why — so the client understands)
  • Applicable limits and how they interact
  • Deductible obligations
  • Subrogation potential (can the insurer recover costs from a third party?)
  • Any coordination of benefits considerations

Documentation Checklist

Gathered:

  • (Items the user indicates are already collected)

Still Needed:

  • Police report (if applicable)
  • Photos of damage
  • Repair estimates (minimum 2–3)
  • Medical records and bills (if injury involved)
  • Witness statements and contact information
  • Receipts for damaged personal property
  • Temporary living expense receipts (if applicable)
  • Business interruption records (if commercial)
  • (Other items specific to the claim type)

Customize this checklist based on the type of loss described.

Read the full file on GitHub · 91 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. 23d ago First seen · 91 lines · 10 tokens per session scan A af29c0d5cc33

Subscribe to this mod's changes

claims-doc is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 10 tokens to every session and 773 once invoked, about $0.0000 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-09-24.