coverage-check

coverage-check is a skill for Claude Code from tylergibbs1/backwork-mcp. It costs 42 tokens per session (1,186 once invoked), scanned A, original, MIT.

A workflow for checking a payer's policy to see how it treats a CPT or HCPCS medical billing code, including conditions and a citation.

In plain words
What is it for?
Use it for questions such as whether a named payer's policy covers a particular medical service code.
Why use it?
It replaces broad, unsupported coverage assumptions with information taken from the payer's policy.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the backwork plugin — 4 skills, 2 commands, 1 MCP server shipped together

Good fit Use it for questions such as whether a named payer's policy covers a particular medical service code.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tylergibbs1/backwork-mcp/coverage-check
Install

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.

Any agent
npx skills add tylergibbs1/backwork-mcp --skill coverage-check
Clone the repo
git clone --depth 1 https://github.com/tylergibbs1/backwork-mcp

Made for: Claude Code.

Or install backwork, the plugin that ships this one along with the rest of its 4 skills, 2 commands, 1 MCP server.

Wrote 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.

agentmods badge for coverage-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/tylergibbs1/backwork-mcp/coverage-check/github.svg)](https://agentmods.dev/skills/tylergibbs1/backwork-mcp/coverage-check)
Your own site
<a href="https://agentmods.dev/skills/tylergibbs1/backwork-mcp/coverage-check"><img src="https://agentmods.dev/badge/skills/tylergibbs1/backwork-mcp/coverage-check/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.

agentmods 80×15 button for coverage-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/tylergibbs1/backwork-mcp/coverage-check"><img src="https://agentmods.dev/badge/skills/tylergibbs1/backwork-mcp/coverage-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,186 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.01186
Opus 5.5 $0.00017 $0.00474
Sonnet 5.5 $0.00008 $0.00237
Haiku 4.5 $0.00004 $0.00119

Measured 15d ago against content hash 6540c415bfc5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

coverage-check 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 15d 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.

plugins/backwork/skills/coverage-check/SKILL.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Coverage check

Answer "is code X covered by payer Y" from Backwork policy data, with a citation for every statement.

The tools come from the Backwork MCP server. Their names start with backwork_. Some clients add a prefix, for example mcp__plugin_backwork_backwork__backwork_coverage_lookup. If no Backwork tool is available, tell the user to connect Backwork (https://backworkhealth.com/mcp) and stop. Do not answer from general knowledge.

Ground rules

  • Research support, not a determination. Report what the policy says. Never say a service "is covered" or "is medically necessary" for a patient. End every answer with: "Confirm with the payer before you submit or schedule."
  • No PHI. Never ask for or accept patient names, member IDs, dates of birth, MRNs, addresses, or chart notes. If the user pastes any, do not repeat it. Ask them to remove it, and continue with codes, payer, state, plan type, and policy as-of date only. Send only those values to the tools.
  • Cite from tool output only. Each policy citation needs: policy number (policy_id), title, payer or authority, effective date, and source URL. Add the last-verified date when the tool returns it. A field the tool did not return is written "not returned". Never fill it in from memory.
  • Inferred codes are not document-backed. A code with source: inferred_title_match is attached because the policy title names the drug. The document does not list the code. Label it "Inferred from policy title. Confirm in the document." A code with source: document (or no source) is listed in the document.
  • Say when you don't know. If the tools return no policy for this payer and code, say "Backwork has no policy on file for and ." Do not guess and do not substitute another payer's policy without saying so.

Steps

  1. Get the inputs: payer, one or more CPT/HCPCS codes. Optional: state (two letters), plan type, policy as-of date (the date whose policy version applies). If payer or code is missing, ask for it.
  2. Call backwork_coverage_lookup with procedure_codes, payer, state, plan_type, date_of_service (the policy as-of date), include: ["code_details", "prior_auth"], and code_include: ["policies"].
  3. From the returned policies, keep the ones that match the payer (for traditional Medicare: NCDs, and LCDs or Articles for the state's MAC jurisdiction). If none match, call backwork_policy_research with action: "search", query set to the code (or drug name for a J-code), and payer.
  4. For each matching policy (at most three), call backwork_policy_research with action: "get", policy_id, and include: ["criteria", "codes"]. Read the code's source and the indications and limitations criteria.
  5. Write the answer in the format below.

Read the full file on GitHub · 63 lines

Changes

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.

  1. 15d ago First seen · 63 lines · 42 tokens per session scan A 6540c415bfc5

Subscribe to this mod's changes

coverage-check is a skill published in the GitHub repository tylergibbs1/backwork-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 1,186 once invoked, about $0.0002 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-10-02.

Related

Other skills, from other repositories

fto-triage

Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…

anthropics/claude-for-legal · 81 tokens

legal-hold

Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.

anthropics/claude-for-legal · 68 tokens

specification-writing

A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.

wanshuiyin/Auto-claude-code-research-in-sleep · 49 tokens

x-scorecard

OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

x-cmd/x-cmd · 57 tokens

regulatory-research-fallback

Fallback workflow for regulatory research when web extraction tools fail on government PDFs.

HKUDS/OpenSpace · 20 tokens

gesellschaftsrechtliche-satzungen-agb

Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.

Klotzkette/claude-fuer-deutsches-recht · 69 tokens