What is follow-up-task-generator?

A helper that reviews recent patient events and creates structured follow-up tasks. It considers visits, changing conditions, lab and imaging results, procedures, and medication changes, then assigns urgency, an owner, and a due date.

Use it to identify pending actions, create follow-up orders or tasks, and organize who should act and when.

It turns scattered clinical findings into specific action items instead of leaving follow-up work to be tracked manually.

follow-up-task-generator — 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 follow-up-task-generator

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/follow-up-task-generator/github.svg)](https://agentmods.dev/skills/langcare/langcare-mcp-fhir/follow-up-task-generator)

Your own site

<a href="https://agentmods.dev/skills/langcare/langcare-mcp-fhir/follow-up-task-generator"><img src="https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/follow-up-task-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.

Your own site · 80×15

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

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

When invoked 4,228 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.00094	$0.04228
Opus 5.5	$0.00038	$0.01691
Sonnet 5.5	$0.00019	$0.00846
Haiku 4.5	$0.00009	$0.00423

Measured 2mo ago against content hash 9c314ea0a037, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

follow-up-task-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 2mo 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.

skills/core/care-coordination/follow-up-task-generator/SKILL.md · 385 lines

How it starts

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

Follow-Up Task Generator

Overview

Analyze a patient's recent clinical data -- encounters, condition changes, lab results, procedures, and medication changes -- to identify required follow-up actions. Generate FHIR Task resources for each follow-up item with appropriate urgency classification (urgent, soon, routine), responsible party assignment, and due dates based on clinical standards.

FHIR Resources Used

Resource	Purpose	Key Fields
Task	Generated follow-up tasks	status, priority, code, for, owner, requester, restriction.period, description, focus, reasonReference
Encounter	Recent visits triggering follow-up	type, period, reasonCode, class
Condition	Active/new conditions requiring monitoring	code, clinicalStatus, onsetDateTime, category
Observation	Lab results requiring follow-up	code, valueQuantity, interpretation, effectiveDateTime, referenceRange
Procedure	Recent procedures requiring post-procedure follow-up	code, performedDateTime, status
MedicationRequest	Medication changes requiring monitoring	medicationCodeableConcept, status, authoredOn, dosageInstruction
DiagnosticReport	Imaging/pathology requiring follow-up	code, conclusion, status
Practitioner	Provider assignment	name, identifier, specialty
ServiceRequest	Existing pending orders	status, code, intent

Instructions

Step 1: Retrieve Recent Encounter

Tool: fhir_search
resourceType: "Encounter"
queryParams: "patient=[patient-id]&_sort=-date&_count=3"

Identify the encounter(s) triggering follow-up generation. Extract: encounter type, date, reason, provider.

Step 2: Retrieve Abnormal Lab Results

Tool: fhir_search
resourceType: "Observation"
queryParams: "patient=[patient-id]&category=laboratory&date=ge=[30-days-ago]&_sort=-date"

Identify results requiring follow-up by checking:

interpretation field: "H" (high), "L" (low), "HH" (critical high), "LL" (critical low), "A" (abnormal)
Values outside referenceRange
Critical values requiring immediate action (see references/task-prioritization.md)
Results that are preliminary or need confirmation

Read the full file on GitHub · 385 lines

Files

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.

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.

2mo ago First seen · 385 lines · 94 tokens per session scan A 9c314ea0a037

Subscribe to this mod's changes

follow-up-task-generator is a skill published in the GitHub repository langcare/langcare-mcp-fhir (71 stars, last pushed 6mo ago), licensed MIT. It adds 94 tokens to every session and 4,228 once invoked, about $0.0004 per session on Opus 5.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.

Planning

follow-up-task-generator next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
follow-up-task-generatorlangcare/langcare-mcp-fhir	Skill	71	6mo ago	MIT	A	94	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code