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 sigistry/marketplace --skill fhir-project-doctorgit clone --depth 1 https://github.com/sigistry/marketplaceWrote 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/sigistry/marketplace/fhir-project-doctor)<a href="https://agentmods.dev/skills/sigistry/marketplace/fhir-project-doctor"><img src="https://agentmods.dev/badge/skills/sigistry/marketplace/fhir-project-doctor/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/sigistry/marketplace/fhir-project-doctor"><img src="https://agentmods.dev/badge/skills/sigistry/marketplace/fhir-project-doctor.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.00088 | $0.00434 |
| Opus 5 | $0.00044 | $0.00217 |
| Sonnet 5 | $0.00018 | $0.00087 |
| Haiku 4.5 | $0.00009 | $0.00043 |
Grade A, and why
fhir-project-doctor 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.
What it actually says
FHIR Project Doctor
Diagnose the project before changing resources or installing tooling. Do not validate or repair clinical content unless the user separately asks for $fhir-validation.
Bundled paths
Resolve <skill-root> to the directory containing this SKILL.md and <plugin-root> two directories above it. Shared deterministic tools live under <plugin-root>/skills/fhir-validation/scripts. Never resolve them relative to the user's workspace.
Workflow
-
Run the detector, runtime planner, and package doctor:
node "<plugin-root>/skills/fhir-validation/scripts/detect-fhir-project.mjs" <target> node "<plugin-root>/skills/fhir-validation/scripts/plan-runtime.mjs" <target> node "<plugin-root>/skills/fhir-validation/scripts/doctor-packages.mjs" <target> -
Separate findings into project signals, runtime availability, FHIR-version compatibility, missing packages, and actions requiring consent.
-
Prefer already configured local tools. Do not install tools, download packages, contact terminology services, or access FHIR URLs without explicit consent.
-
Treat missing declared packages and mixed/unsupported FHIR versions as blockers for claims of profile-aware validation.
-
Recommend the smallest next action. Do not claim that structural fallback proves profile, invariant, terminology, canonical, or cross-document-reference conformance.
Output
Report the selected runtime, privacy boundary, detected FHIR version(s), validation depth available, package blockers, and ordered next actions. Preserve the tools' schemaVersion, tool, mode, capabilities, warnings, and nextActions fields when summarizing.
What ships with it
3 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 · 32 lines · 88 tokens per session scan A c64bb18603f8
fhir-project-doctor is a skill published in the GitHub repository sigistry/marketplace (3 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 434 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-09-03.
Other skills, from other repositories
architecture-optimization
Guided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer …
improve-code-quality
Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy…
remove-technical-debt
Guided journey from a large aged codebase everyone fears to touch to one that is safe to change, legible, bounded, and resilient - paid down in place without a rewrite. Orchestrates eight skills phase by phase - working-with-legacy-code, refactoring-patterns, clean-code, software-design-philosophy, clean-architecture…
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…
verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
ask-codex
Consult OpenAI Codex for investigation, debugging, or code review. Use when user explicitly asks to "ask codex", "check with codex", "codex review", or as a last resort when stuck after 4+ failed attempts at debugging, investigation, or bug fix and completely out of ideas. Codex is slow (2-5 min), so only escalate…