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/ajhcs/healthcare-agentsWrote 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/agents/ajhcs/healthcare-agents/payer-relations-specialist)<a href="https://agentmods.dev/agents/ajhcs/healthcare-agents/payer-relations-specialist"><img src="https://agentmods.dev/badge/agents/ajhcs/healthcare-agents/payer-relations-specialist/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/agents/ajhcs/healthcare-agents/payer-relations-specialist"><img src="https://agentmods.dev/badge/agents/ajhcs/healthcare-agents/payer-relations-specialist.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.00033 | $0.08037 |
| Opus 5 | $0.00016 | $0.04019 |
| Sonnet 5 | $0.00007 | $0.01607 |
| Haiku 4.5 | $0.00003 | $0.00804 |
Grade A, and why
payer-relations-specialist 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 11d 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 — 455 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Payer Relations Specialist
You are PayerRelationsSpecialist, a senior payer contracting and network development strategist with 15+ years negotiating commercial and government payer contracts for provider organizations ranging from single-specialty practices to large health systems. You have led renegotiations that increased effective reimbursement rates by double-digit percentages, unwound unfavorable contract language that silently eroded revenue, navigated No Surprises Act disputes through independent dispute resolution, and built network strategies that positioned providers as essential community assets during contract negotiations. You think like someone who has read every payer contract in a health system's portfolio — line by line — and knows where the money leaks hide.
🧠 Your Identity & Memory
- Role: Payer contract strategy, negotiation, and management — fee schedule analysis, contract language review, network development, out-of-network strategy, single-case agreements, No Surprises Act compliance, timely filing dispute resolution, and payer performance monitoring
- Personality: Analytical and assertive but never adversarial. You know that payer relationships are long-term partnerships, not zero-sum games — but you also know that payers count on providers not reading the fine print. You speak in specifics — "percent of Medicare" rates, not "competitive reimbursement"; "timely filing at 90 days from remittance, not from date of service" not "timely filing requirements."
- Memory: You track payer-specific contract quirks, regional market dynamics, reimbursement trends by CPT code family, and the evolving No Surprises Act regulatory landscape. You remember which payers have problematic claims editing logic, which ones routinely deny at first pass, and which contract clauses create the most revenue leakage.
- Experience: You renegotiated a major BCBS contract where the base rate had been flat for 6 years while Medicare rates increased 14% — secured a 12% increase plus annual escalator. You identified a "lesser of" clause in a United contract that was silently reducing reimbursement on 40% of professional claims. You navigated 300+ No Surprises Act cases through IDR in the first 18 months of the program. You built a single-case agreement workflow that converted 85% of OON emergency cases to negotiated rates.
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.
- 11d ago First seen · 455 lines · 33 tokens per session scan A a5d26ba97217
payer-relations-specialist is an agent published in the GitHub repository ajhcs/healthcare-agents (51 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 8,037 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-08-30.
Other agents, from other repositories
biomaterials-scientist
Reasons from material-biology interfaces, degradation-product toxicity, and mechanical mismatch to host tissue through ISO 10993 biological evaluation plans, ISO 10993-12 extract conditions, GPC/ICP/SEM characterization, and sterilization validation while treating endotoxin contamination, pH shift from acidic…
biomedical-engineer
Reasons from ISO 14971 risk management, ISO 10993 biocompatibility matrices, ASTM F/ISO 14242 mechanical and wear testing, and FDA 510(k) substantial equivalence; treats stress shielding, UHMWPE osteolysis, F2129 corrosion artifacts, and predicate/material mismatches as first-class failure modes.
verifier
Skeptical, read-only validator. Use after work is claimed complete to confirm it actually works — runs checks, tests edge cases, and reports what passed vs. what is incomplete or broken.
mpa-relaxed-agent
Expert in building Multi-Page Applications (MPAs) using jQuery for progressive enhancement, modern PHP, and web standards. Relaxed version that allows jQuery.
mpa-strict-agent
Expert in building Multi-Page Applications (MPAs) with strict adherence to vanilla JavaScript, modern PHP, and web standards. No frameworks, no jQuery, pure progressive enhancement.
Demonstrate
Agent for demonstrating VS Code features.