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 oncology-treatment-timelinegit 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/oncology-treatment-timeline)<a href="https://agentmods.dev/skills/langcare/langcare-mcp-fhir/oncology-treatment-timeline"><img src="https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/oncology-treatment-timeline/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/oncology-treatment-timeline"><img src="https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/oncology-treatment-timeline.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.00108 | $0.04418 |
| Opus 5 | $0.00054 | $0.02209 |
| Sonnet 5 | $0.00022 | $0.00884 |
| Haiku 4.5 | $0.00011 | $0.00442 |
Grade A, and why
oncology-treatment-timeline 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 — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Oncology Treatment Timeline
Overview
Construct a comprehensive cancer treatment timeline from FHIR resources. Pull cancer diagnosis Conditions with staging data, chemotherapy MedicationRequests, surgical and radiation Procedures, tumor marker Observations, and imaging DiagnosticReports. Organize chronologically into phases: diagnosis/staging, neoadjuvant treatment, definitive treatment (surgery/radiation), adjuvant treatment, response assessment, and surveillance. Track treatment response through tumor marker trends and imaging results using RECIST criteria where applicable. Identify current treatment phase and upcoming milestones.
FHIR Resources Used
| Resource | Purpose | Key Fields |
|---|---|---|
| Patient | Demographics, age | birthDate, gender |
| Condition | Cancer diagnosis, staging, comorbidities | code, stage, clinicalStatus, onsetDateTime |
| MedicationRequest | Chemotherapy regimens, supportive care | medicationCodeableConcept, status, dosageInstruction, authoredOn |
| Procedure | Surgery, radiation, biopsy | code, performedDateTime, status, outcome |
| Observation | Tumor markers, performance status, lab values | code, valueQuantity, effectiveDateTime, interpretation |
| DiagnosticReport | Pathology, imaging | code, conclusion, result, effectiveDateTime |
| CarePlan | Treatment plan documentation | category, activity, status |
Instructions
Step 1: Retrieve Patient Demographics
Tool: fhir_read
resourceType: "Patient"
id: "[patient-id]"
Extract age, gender. Relevant for gender-specific cancers and age-adjusted treatment protocols.
Step 2: Pull Cancer Diagnosis
Tool: fhir_search
resourceType: "Condition"
queryParams: "patient=[patient-id]&category=encounter-diagnosis&code:below=363346000"
SNOMED 363346000 = Malignant neoplastic disease (parent concept). This captures all malignant neoplasm subtypes.
If SNOMED search fails, try ICD-10 range:
Tool: fhir_search
resourceType: "Condition"
queryParams: "patient=[patient-id]&code:below=C00"
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.
- 9d ago First seen · 370 lines · 108 tokens per session scan A 31807a806e73
oncology-treatment-timeline is a skill published in the GitHub repository langcare/langcare-mcp-fhir (55 stars, last pushed 5mo ago), licensed MIT. It adds 108 tokens to every session and 4,418 once invoked, about $0.0005 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-09-03.
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…