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-requirements-contract-reviewgit 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-requirements-contract-review)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/insurance-requirements-contract-review"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/insurance-requirements-contract-review/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-requirements-contract-review"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/insurance-requirements-contract-review.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.00037 | $0.02111 |
| Opus 5 | $0.00018 | $0.01056 |
| Sonnet 5 | $0.00007 | $0.00422 |
| Haiku 4.5 | $0.00004 | $0.00211 |
Grade A, and why
Insurance Requirements Contract Review 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Insurance Requirements Contract Review
Purpose
Review the insurance and indemnity provisions of a contract — lease, master services agreement, vendor agreement, construction agreement, service agreement, or purchase agreement — into a source-cited requirements table, a risk matrix, a missing-provisions list, and negotiation points for attorney review. This skill organizes what the contract requires and flags gaps from the user's perspective; it reaches no conclusion that the requirements are legally sufficient.
Use When
- The insurance and indemnity clauses of a contract must be reviewed and organized for an attorney.
- A party needs the required policies, limits, endorsements, and indemnity terms mapped from its perspective.
- Missing or one-sided insurance provisions must be flagged before negotiation or signing.
Required Inputs
- The contract, with the insurance and indemnity clauses, and source references.
- The contract type (lease, MSA, vendor agreement, construction agreement, service agreement, purchase agreement, or other) — or
not provided. - The user's role (the party requiring coverage, the party providing it, landlord, tenant, owner, contractor, customer, vendor, or other) — or
not provided. - Optional but recommended: the user's standard insurance requirements or playbook.
- Optional: the practice group's
practice-profiles/insurance.mdif it has been populated and is loaded alongside this skill. If present, the skill uses its Standard Positions and Escalation Thresholds tables to benchmark the output and to gate escalation. If absent, the skill proceeds without practice-profile benchmarking and asks the user to supply standing positions inline if needed. - Any dates or notice periods in the clauses, echoed and marked
[deadline verification required]. - Jurisdiction and governing law, or
[verify jurisdiction]— anti-indemnity and insurance-procurement rules are jurisdiction-specific.
If the contract or the insurance/indemnity clauses are missing, record it as not provided and return the missing-information list first. Do not review from a description alone.
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 · 119 lines · 37 tokens per session scan A ee1ce83198ce
Insurance Requirements Contract Review is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 2,111 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
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.
redline-sentry
Review NDAs, MSAs, DPAs, SaaS agreements, and other procurement contracts against a configurable risk playbook. Use whenever the user drops a contract file (PDF, DOCX) and asks to redline, review, summarise risk, check clauses, or "what would procurement say". Trigger on phrases like "review this NDA", "redline this…
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…