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 coverage-position-outlinegit 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/coverage-position-outline)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/coverage-position-outline"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/coverage-position-outline/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/coverage-position-outline"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/coverage-position-outline.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.00027 | $0.01737 |
| Opus 5 | $0.00014 | $0.00869 |
| Sonnet 5 | $0.00005 | $0.00347 |
| Haiku 4.5 | $0.00003 | $0.00174 |
Grade A, and why
Coverage Position Outline 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coverage Position Outline
Purpose
Assemble a structured, source-cited coverage-position outline from supplied policy and claim materials — facts, policy provisions, potential coverage grants, exclusions, endorsements, conditions, notice and cooperation, posture, and open issues — so a coverage attorney can develop and decide the position. This skill produces an outline only; it states no coverage conclusion and drafts no opinion or denial.
Use When
- A coverage attorney needs the materials organized into a position outline before drafting an analysis.
- The policy and claim file must be structured so candidate grants, exclusions, and open issues are visible.
- A reviewer wants the analytical skeleton, with every coverage decision left to counsel.
Required Inputs
- The policy or a completed
insurance-policy-summary, with source references. - The claim facts as provided, and any tender, pleadings, demand letters, correspondence, reservation of rights, or prior coverage analysis, with source references.
- The policy type — or
not provided. - The user's role (insurer-side, insured-side, coverage counsel, or other) — or
not provided. - The claim type and the claim stage — or
not provided. - Any policy or claim dates, echoed and marked
[deadline verification required]. - Jurisdiction and governing law, or
[verify jurisdiction].
If the policy, the claim facts, the policy type, or the role is missing, record it as not provided and return the missing-information list first.
Do Not Use When
- The request is to decide coverage, a duty to defend, or a duty to indemnify.
- The request is to draft a final coverage opinion or a denial letter as a usable document.
- The request is to recommend granting or denying coverage, or for legal advice.
- A source-grounded summary is all that is needed (use
insurance-policy-summary), or the issues are not yet spotted (usecoverage-issue-spotter).
Also out of scope (this skill does not): decide whether a claim is covered; conclude on a duty to defend or indemnify; decide which exclusion or endorsement applies; resolve ambiguity; draft a coverage opinion or a final denial letter; recommend that coverage be granted or denied; 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 · 113 lines · 27 tokens per session scan A 859051d79913
Coverage Position Outline is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 1,737 once invoked, about $0.0001 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
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-interpretation
Analyze legal documents (statutes, contracts, constitutions, treaties, and regulatory texts) using a cross-jurisdictional framework of legal interpretation.
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.
legal-discovery
Audit e-discovery and litigation document review systems -- data collection pipelines (PST, MBOX, SharePoint, Slack), document processing (OCR via Tesseract/ABBYY, metadata extraction, deduplication), Technology Assisted Review (TAR 1.0/2.0/CAL with recall/precision tracking).