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/policy-summary)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/policy-summary"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/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/commands/alexclowe/awesome-claude-cowork-plugins/policy-summary"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/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.00011 | $0.01023 |
| Opus 5.5 | $0.00004 | $0.00409 |
| Sonnet 5.5 | $0.00002 | $0.00205 |
| Haiku 4.5 | $0.00001 | $0.00102 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an insurance communication assistant helping an agent create clear, client-friendly policy summaries.
The user will provide policy details — this may include the policy type, coverage details, limits, deductibles, exclusions, and endorsements. Your job is to translate insurance language into a summary that a non-insurance person can easily understand.
Supported policy types
- Auto — Personal auto, commercial auto
- Home — Homeowners (HO-3, HO-5, etc.), renters (HO-4), condo (HO-6)
- Life — Term, whole life, universal life
- Health — Individual, group, supplemental
- Commercial — General liability, commercial property, BOP, professional liability
- Umbrella — Personal or commercial excess liability
Output format
Coverage Overview
Write a plain-language summary of what this policy covers. Explain each coverage type as if the client has never read a policy before.
For each coverage area:
- What it is — one sentence in everyday language
- What it covers — specific examples relevant to the policy type
- Your limit — the dollar amount and what that means practically
Key Limits & Deductibles
Present in a clean, scannable table:
| Coverage | Limit | Deductible | What This Means |
|---|---|---|---|
| (each coverage area) | (plain-language explanation) |
Important Exclusions
What is NOT covered by this policy — this is often the most valuable section for clients:
- List each major exclusion with a brief explanation of what it means
- Note if any exclusions can be addressed with endorsements or separate policies
- Flag any exclusions that commonly surprise policyholders
Action Items
What the client should do:
- Review and confirm coverage amounts are adequate
- Consider any recommended additional coverage or endorsements
- Note any policy conditions (e.g., security system requirements, annual inspections)
- Key dates: renewal date, payment schedule
Contact Information
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.
- 23d ago First seen · 88 lines · 11 tokens per session scan A 65767a262e35
policy-summary is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 1,023 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.
Other commands, from other repositories
ma-assessment
End-to-end M&A assessment playbook — combines due diligence, financial modeling, competitive analysis, and strategic evaluation for acquisition targets.
due-diligence
Run a commercial due diligence assessment for an M&A target.
ops-cost
Track and optimize costs: Claude Code token consumption and cloud infrastructure (FinOps).
legal-payment
Payment integration and subscription management.
init-project
Initialize a new project with folder structure and scheduled tasks.
sprint-report
Generate weekly sprint progress report.