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 PolicyEngine/policyengine-claude --skill policyengine-healthcaregit clone --depth 1 https://github.com/PolicyEngine/policyengine-claudeWrote 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/policyengine/policyengine-claude/policyengine-healthcare)<a href="https://agentmods.dev/skills/policyengine/policyengine-claude/policyengine-healthcare"><img src="https://agentmods.dev/badge/skills/policyengine/policyengine-claude/policyengine-healthcare/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/policyengine/policyengine-claude/policyengine-healthcare"><img src="https://agentmods.dev/badge/skills/policyengine/policyengine-claude/policyengine-healthcare.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
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.00246 | $0.02610 |
| Opus 5 | $0.00123 | $0.01305 |
| Sonnet 5 | $0.00049 | $0.00522 |
| Haiku 4.5 | $0.00025 | $0.00261 |
Grade A, and why
policyengine-healthcare 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PolicyEngine US healthcare domain knowledge
Medicaid, the ACA marketplace (premium tax credit), CHIP, and Medicare are the hardest US programs
to analyze correctly, because they are modeled as in-kind health benefits rather than cash.
This skill is the domain layer for analysts using the policyengine package; for non-health US
programs use policyengine-us, for the shared calculation/reform mechanics use the
policyengine skill, and for building new health variables use policyengine-model-development.
Verified against policyengine 4.21.0 / policyengine-us 1.764.6 (2026-07). Re-verify variable names and parameter values before reporting.
The one gotcha that dominates everything: health benefits are excluded from net income
gov.simulation.include_health_benefits_in_net_income defaults to False. ACA PTC, Medicaid,
CHIP, and Medicare cost flow through household_health_benefits, which the default
household_net_income does not include. So a reform that changes aca_ptc or medicaid
produces a $0 change in household_net_income — the single biggest time-sink in health
analysis. If you score a PTC or Medicaid reform by net-income change and get zero, this is why.
Measure health impact one of these ways instead:
household_net_income_including_health_benefits— the same net income with health benefits folded in. Its difference fromhousehold_net_incomeis exactly the household's health-benefit value.- The program variable directly —
aca_ptc(tax_unit),medicaid(person), summed or differenced across baseline and reform. - Population cost:
pe.us.calculate_budgetary_impact. Itstotalalready adds the shared-funding health-program cost (Medicaid / CHIP / Medicare Savings Programs) on top of Δtax − Δbenefits, so it captures the health split automatically — do not hand-roll it fromhousehold_net_income. See the policyengine skill for the population flow.
Verified end to end (single adult, $35k, Texas — ACA-eligible, not Medicaid-eligible):
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 · 188 lines · 246 tokens per session scan A b7e3d323cc96
policyengine-healthcare is a skill published in the GitHub repository PolicyEngine/policyengine-claude (32 stars, last pushed 3d ago), licensed MIT. It adds 246 tokens to every session and 2,610 once invoked, about $0.0012 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 skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…