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 history-and-physical-generatorgit 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/history-and-physical-generator)<a href="https://agentmods.dev/skills/langcare/langcare-mcp-fhir/history-and-physical-generator"><img src="https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/history-and-physical-generator/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/history-and-physical-generator"><img src="https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/history-and-physical-generator.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.00114 | $0.03962 |
| Opus 5 | $0.00057 | $0.01981 |
| Sonnet 5 | $0.00023 | $0.00792 |
| Haiku 4.5 | $0.00011 | $0.00396 |
Grade A, and why
history-and-physical-generator 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 13d 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 — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.
History and Physical Generator
Overview
Generate a comprehensive History and Physical document from FHIR resources. Auto-populate all available structured data including past medical history, past surgical history, medication list, allergy list, family history, social history, and current vital signs/labs. Flag data gaps requiring clinician input. Support regulatory requirements for admission H&P per CMS CoP and TJC standards (must be completed within 24 hours of admission, updated within 30 days if pre-admission H&P exists).
FHIR Resources Used
| Resource | Purpose | Key Fields |
|---|---|---|
| Patient | Demographics, social determinants | name, birthDate, gender, communication, extension |
| Encounter | Admission context, reason for admission | class, reasonCode, period, hospitalization |
| Condition | PMH, current diagnoses | code, clinicalStatus, onsetDateTime, category |
| Procedure | Past surgical history | code, performedDateTime, status |
| MedicationRequest | Current and home medications | medicationCodeableConcept, dosageInstruction, status |
| AllergyIntolerance | Allergies and adverse reactions | code, reaction, clinicalStatus, criticality |
| FamilyMemberHistory | Family medical history | relationship, condition, deceasedBoolean |
| Observation | Vitals, labs, social history | code, value[x], category, effectiveDateTime |
| DocumentReference | Prior H&P documents | type, content, date |
| CarePlan | Existing care plans | status, intent, category, activity |
Instructions
Step 1: Retrieve Admission Encounter
Tool: fhir_read
resourceType: "Encounter"
id: "[encounter-id]"
Extract:
- Admitting diagnosis:
reasonCodearray - Admission date/time:
period.start - Encounter class:
class.code(IMP = inpatient, OBSENC = observation) - Admitting physician:
participantwheretype.coding.code= "ADM" - Source of admission:
hospitalization.admitSource
If no encounter ID provided:
Tool: fhir_search
resourceType: "Encounter"
queryParams: "patient=[patient-id]&class=IMP&status=in-progress&_sort=-date&_count=1"
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 13d ago First seen · 418 lines · 114 tokens per session scan A 7cc5bf433fe3
history-and-physical-generator is a skill published in the GitHub repository langcare/langcare-mcp-fhir (55 stars, last pushed 5mo ago), licensed MIT. It adds 114 tokens to every session and 3,962 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…