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 bad-faith-risk-triagegit 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/bad-faith-risk-triage)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/bad-faith-risk-triage"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/bad-faith-risk-triage/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/bad-faith-risk-triage"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/bad-faith-risk-triage.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.00038 | $0.01753 |
| Opus 5 | $0.00019 | $0.00877 |
| Sonnet 5 | $0.00008 | $0.00351 |
| Haiku 4.5 | $0.00004 | $0.00175 |
Grade A, and why
Bad Faith Risk Triage 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bad Faith Risk Triage
Purpose
Issue-spot potential claim-handling and bad-faith risk themes from claim file materials — investigation timeline, communications, delays, coverage explanations, information requests, settlement demands, defense handling, conflicts, documentation, and escalation — into a source-cited risk-theme list for attorney review. This skill surfaces themes a coverage or bad-faith attorney must evaluate; it concludes nothing about whether bad faith occurred.
Use When
- A claim file must be triaged for potential claim-handling and bad-faith risk themes before attorney review.
- Counsel needs the file's risk themes, chronology gaps, and communication issues organized and sourced.
- An insurer or insured wants potential exposure themes surfaced for a bad-faith or claim-handling assessment.
Required Inputs
- The claim file materials — adjuster or examiner notes, claim correspondence, coverage letters (reservation of rights, denials), settlement demands and offers, defense-counsel materials, and the claim diary, with source references.
- The policy or a completed
insurance-policy-summary, and any completedclaims-chronology-builder, with source references. - The policy type — or
not provided. - The user's role (insurer-side, insured-side, claimant-side, counsel, or other) — or
not provided. - The claim type and the claim stage — or
not provided. - Any dates in the file, echoed and marked
[deadline verification required]. - Jurisdiction and governing law, or
[verify jurisdiction]— bad-faith and claim-handling standards are jurisdiction-specific.
If the claim file, 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 conclude whether bad faith occurred or did not occur.
- The request is to decide whether claim handling was reasonable, in good faith, or compliant with any claim-handling standard or statute.
- The request is to assess extracontractual or punitive exposure, damages, or settlement value.
- The request is for legal advice or a litigation prediction.
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 · 117 lines · 38 tokens per session scan A 1de530a1b84f
Bad Faith Risk Triage is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,753 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.
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…
aenderungsvorbehalt-308
Für Änderungsvorbehalt 308: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.