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 langcare/langcare-mcp-fhir --skill problem-list-auditgit clone --depth 1 https://github.com/langcare/langcare-mcp-fhirWrote 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/langcare/langcare-mcp-fhir/problem-list-audit)<a href="https://agentmods.dev/skills/langcare/langcare-mcp-fhir/problem-list-audit"><img src="https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/problem-list-audit/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/langcare/langcare-mcp-fhir/problem-list-audit"><img src="https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/problem-list-audit.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.00067 | $0.00758 |
| Opus 5 | $0.00034 | $0.00379 |
| Sonnet 5 | $0.00013 | $0.00152 |
| Haiku 4.5 | $0.00007 | $0.00076 |
Grade A, and why
langcare-problem-list-audit 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 12d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Problem List Audit
When to Use This Skill
Use when a clinician needs to validate the accuracy and completeness of a patient's active problem list by cross-referencing against medications, lab results, and encounter history.
Clinical Workflow
- Use
fhir_searchto pull all Condition resources (active, resolved, inactive) for the patient - Use
fhir_searchto pull active MedicationRequest resources -- infer expected diagnoses from medications (e.g., metformin implies diabetes, levothyroxine implies hypothyroidism) - Use
fhir_searchto pull recent Observation (laboratory) results -- infer conditions from abnormal lab patterns (e.g., elevated HbA1c implies diabetes, elevated TSH implies hypothyroidism) - Use
fhir_searchto pull recent Encounter resources and their associated Condition resources (encounter diagnoses) to find conditions documented in visits but missing from the problem list - Cross-reference all sources: flag medications without a supporting active problem, lab patterns without a corresponding diagnosis, encounter diagnoses not on the active problem list, and active problems with no supporting evidence in recent encounters/medications/labs
FHIR Resources
- Condition -- Problem list entries with clinicalStatus, verificationStatus, code (ICD-10/SNOMED), onset, abatement
- MedicationRequest -- Active medications implying diagnoses
- Observation -- Lab results with patterns suggesting undiagnosed conditions
- Encounter -- Recent visits with encounter-specific diagnoses
FHIR Query Examples
Pull All Conditions
fhir_search(resourceType="Condition", queryParams="patient=[patient-id]&_count=200")
Pull Active Medications
fhir_search(resourceType="MedicationRequest", queryParams="patient=[patient-id]&status=active&_count=100")
Pull Recent Encounter Diagnoses
fhir_search(resourceType="Encounter", queryParams="patient=[patient-id]&date=ge[12-months-ago]&_sort=-date&_count=50")
Clinical Guidelines
- CMS requires accurate problem list maintenance for quality reporting and risk adjustment (HCC coding)
- ICD-10 coding specificity requirements: prefer specific codes (E11.65 T2DM with hyperglycemia) over unspecified (E11.9)
- SNOMED CT preferred for clinical documentation; ICD-10-CM required for billing
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.
- 12d ago First seen · 61 lines · 67 tokens per session scan A c9c6a95d5297
langcare-problem-list-audit is a skill published in the GitHub repository langcare/langcare-mcp-fhir (55 stars, last pushed 5mo ago), licensed MIT. It adds 67 tokens to every session and 758 once invoked, about $0.0003 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…