What is langcare-pre-op-labs?

A preoperative laboratory checklist evaluates whether a patient has the tests needed before surgery. It considers the operation, age, existing conditions, medications, and ASA classification, a medical estimate of overall surgical risk.

Use it to check laboratory readiness for a planned procedure and flag results or tests that need clinical review before surgery.

It helps identify missing, outdated, or abnormal results that could delay surgical clearance. It uses FHIR, a standard format for exchanging healthcare records, to review patient data.

langcare-pre-op-labs — Skill for Claude Code and Codex by langcare

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 langcare/langcare-mcp-fhir --skill pre-op-labs

Clone the repo

git clone --depth 1 https://github.com/langcare/langcare-mcp-fhir

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/pre-op-labs/github.svg)](https://agentmods.dev/skills/langcare/langcare-mcp-fhir/pre-op-labs)

Your own site

<a href="https://agentmods.dev/skills/langcare/langcare-mcp-fhir/pre-op-labs"><img src="https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/pre-op-labs/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/langcare/langcare-mcp-fhir/pre-op-labs"><img src="https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/pre-op-labs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 795 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.

Model	Per session	Once invoked
Fable 5.1	$0.00072	$0.00795
Opus 5	$0.00036	$0.00398
Sonnet 5	$0.00014	$0.00159
Haiku 4.5	$0.00007	$0.00080

Measured 12d ago against content hash a7aa695ba00f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

langcare-pre-op-labs 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.

cma/skills/lab-diagnostics/pre-op-labs/SKILL.md · 60 lines

How it starts

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

Preoperative Lab Checklist

When to Use This Skill

Use when a clinician needs to verify that all required preoperative laboratory tests have been completed, are within acceptable timeframes, and have acceptable results for surgical clearance.

Clinical Workflow

Use fhir_read to retrieve Patient demographics (age, gender)
Use fhir_search to pull active Condition resources for comorbidity-based lab requirements
Use fhir_search to pull active MedicationRequest resources for medication-based lab requirements (e.g., anticoagulants require coag studies, digoxin requires level and electrolytes)
Use fhir_search to pull scheduled Procedure or ServiceRequest for the planned surgery to determine procedure type
Determine required labs based on: patient age (>45: ECG, BMP; >65: CBC, CMP, ECG), comorbidities (diabetes: glucose/A1c; cardiac: BNP/troponin; renal: BMP/CrCl; liver: LFTs/coags; anemia: CBC/iron), procedure type (blood loss risk: T&S/CBC; cardiac surgery: full panel), medications (anticoagulants: PT/INR; digoxin: level)
Use fhir_search to pull recent Observation resources (laboratory) and check if required labs are present and within acceptable timeframe (typically 30 days, 7 days for coags on anticoagulants)
Flag: missing labs, expired labs (older than required timeframe), abnormal results that may delay surgery

FHIR Resources

Patient -- Age for age-based requirements
Condition -- Comorbidities driving lab requirements
MedicationRequest -- Medications requiring monitoring
Observation -- Lab results to verify completeness and values
ServiceRequest -- Planned procedure for procedure-specific requirements

FHIR Query Examples

Pull Recent Labs (30 days)

fhir_search(resourceType="Observation", queryParams="patient=[patient-id]&category=laboratory&date=ge[30-days-ago]&_sort=-date&_count=200")

Pull Planned Procedure

fhir_search(resourceType="ServiceRequest", queryParams="patient=[patient-id]&status=active&intent=order&category=387713003")

Read the full file on GitHub · 60 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.

12d ago First seen · 60 lines · 72 tokens per session scan A a7aa695ba00f

Subscribe to this mod's changes

langcare-pre-op-labs is a skill published in the GitHub repository langcare/langcare-mcp-fhir (55 stars, last pushed 5mo ago), licensed MIT. It adds 72 tokens to every session and 795 once invoked, about $0.0004 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.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens