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 insurance-policy-summarygit 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/insurance-policy-summary)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/insurance-policy-summary"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/insurance-policy-summary/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/insurance-policy-summary"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/insurance-policy-summary.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.01752 |
| Opus 5 | $0.00017 | $0.00876 |
| Sonnet 5 | $0.00007 | $0.00350 |
| Haiku 4.5 | $0.00003 | $0.00175 |
Grade A, and why
Insurance Policy Summary 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Insurance Policy Summary
Purpose
Summarize an insurance policy into a structured, source-cited overview — declarations, named and additional insureds, policy period, coverage parts, limits, deductibles and self-insured retentions (SIRs), insuring agreements, definitions, exclusions, endorsements, conditions, and the forms schedule — so a qualified attorney can review the policy efficiently. This skill extracts and organizes what the policy documents say; it reaches no conclusion that coverage exists.
Use When
- An insurance policy must be summarized and organized for an attorney before a coverage review, claim review, or renewal.
- A reviewer needs declarations, coverage parts, limits, exclusions, endorsements, and conditions mapped with source citations.
- The policy is a long, definition-heavy document and a source-grounded summary is needed before substantive analysis.
Required Inputs
- The policy document set — declarations, the policy jacket or coverage forms, and all endorsements — with source references (page, form number, endorsement number, section).
- The policy type (for example, commercial general liability, property, professional liability, directors and officers, auto, umbrella/excess, homeowners, life) — or
not provided. - The user's role (insurer, insured, additional insured, claimant, broker, or other) — or
not provided. - The policy period as written, echoed and marked
[deadline verification required]. - The review purpose (claim, renewal, contract compliance, diligence, or other) — or
not provided. - Jurisdiction and governing law if known, or
[verify jurisdiction].
If the policy documents, the policy type, or the policy period is missing, record it as not provided and return the missing-information list first. Do not summarize a policy from a description alone.
Do Not Use When
- The request is to conclude whether a claim is covered, or whether the insurer must defend or indemnify (use
coverage-issue-spotter, then attorney review). - The request is to draft a coverage position, reservation of rights, or denial.
- The request is to interpret ambiguous policy language as a legal matter, or for a coverage opinion or legal advice.
- Only a certificate of insurance is provided, not the policy (use
certificate-of-insurance-review).
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 · 109 lines · 35 tokens per session scan A 1b96c7b95f71
Insurance Policy Summary 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,752 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
cultural-heritage-summary
Produces structured, citation-ready summaries of legal developments in cultural heritage protection covering repatriation, site protection, illicit trafficking, and treaty updates. Use when tracking heritage law, preparing government or NGO briefings, or summarizing international and national decisions. Trigger…
cyber-law-compliance-summary
Produces structured cyber law compliance memoranda covering GDPR, CCPA, state privacy laws, and sector-specific regulations for US and EU operations. Includes Bluebook citations, jurisdiction comparison tables, penalty exposure, and regulatory trends. Use when advising on digital operations compliance, privacy program…
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…