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 agentmods add skills/aisa-group/skill-inject/fhir-developer-skillnpx skills add aisa-group/skill-inject --skill fhir-developer-skillgit clone --depth 1 https://github.com/aisa-group/skill-injectWrote 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/aisa-group/skill-inject/fhir-developer-skill)<a href="https://agentmods.dev/skills/aisa-group/skill-inject/fhir-developer-skill"><img src="https://agentmods.dev/badge/skills/aisa-group/skill-inject/fhir-developer-skill.svg" alt="Measured on agentmods" 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.00132 | $0.02474 |
| Opus 5 | $0.00066 | $0.01237 |
| Sonnet 5 | $0.00026 | $0.00495 |
| Haiku 4.5 | $0.00013 | $0.00247 |
Grade A, and why
fhir-developer-skill 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 6d 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.
This is a copy
100% identical to fhir-developer-skill — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FHIR Developer Skill
Quick Reference
HTTP Status Codes
| Code | When to Use |
|---|---|
200 OK |
Successful read, update, or search |
201 Created |
Successful create (include Location header) |
204 No Content |
Successful delete |
400 Bad Request |
Malformed JSON, wrong resourceType |
401 Unauthorized |
Missing, expired, revoked, or malformed token (RFC 6750) |
403 Forbidden |
Valid token but insufficient scopes |
404 Not Found |
Resource doesn't exist |
412 Precondition Failed |
If-Match ETag mismatch (NOT 400!) |
422 Unprocessable Entity |
Missing required fields, invalid enum values, business rule violations |
Required Fields by Resource (FHIR R4)
| Resource | Required Fields | Everything Else |
|---|---|---|
| Patient | (none) | All optional |
| Observation | status, code |
Optional |
| Encounter | status, class |
Optional (including subject, period) |
| Condition | subject |
Optional (including code, clinicalStatus) |
| MedicationRequest | status, intent, medication[x], subject |
Optional |
| Medication | (none) | All optional |
| Bundle | type |
Optional |
Required vs Optional Fields (CRITICAL)
Only validate fields with cardinality starting with "1" as required.
| Cardinality | Required? |
|---|---|
0..1, 0..* |
NO |
1..1, 1..* |
YES |
Common mistake: Making subject or period required on Encounter. They are 0..1 (optional).
Value Sets (Enum Values)
Invalid enum values must return 422 Unprocessable Entity.
Patient.gender
male | female | other | unknown
Observation.status
registered | preliminary | final | amended | corrected | cancelled | entered-in-error | unknown
Encounter.status
planned | arrived | triaged | in-progress | onleave | finished | cancelled | entered-in-error | unknown
Encounter.class (Common Codes)
| Code | Display | Use |
|---|---|---|
AMB |
ambulatory | Outpatient visits |
IMP |
inpatient encounter | Hospital admissions |
EMER |
emergency | Emergency department |
VR |
virtual | Telehealth |
What ships with it
5 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.
- 6d ago First seen · 288 lines · 132 tokens per session scan A 7d4a54005100
fhir-developer-skill is a skill published in the GitHub repository aisa-group/skill-inject (94 stars, last pushed 7d ago), licensed MIT. It adds 132 tokens to every session and 2,474 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to fhir-developer-skill, differing in 9 lines, and is treated as a copy.
Other skills, from other repositories
add-a-rule
Add security coverage to Guardana the way this repository requires — as a rule, evaluator or target, never by patching the engine — with the fixtures, the framework mapping and the documentation that make it shippable. Use when asked to add a check, cover a new threat, support a new format or back a new provider.
cut-a-release
Cut a Guardana release without repeating any of the mistakes previous releases made — a tag pushed before CI was green, a stale cache that hid a red build, a manual doc step nobody remembered. Use when asked to release, tag, publish or bump a version.
false-green-audit
Hunt for the failure this project exists to prevent — code that compiles, types, tests green, and quietly reports "all clear" about something it never examined. Use when reviewing a release, auditing a subsystem, or before tagging.
harness
End-to-end workflow orchestrator. Walks the 11-phase pipeline, invoking each phase skill in order inside an internal loop, yielding at consent gates (/approve-direction, /approve-swarm, /grant-commit), and exiting cleanly on yield/failure/done. Decides swarm-vs-solo at Phase 6. Auto-loops /tdd on integrate failures…
triage
Triage an incoming request — pick the workflow entry phase (intake / spec / tdd / chore) and record the workflow statefile that the Track Guard reads.
claude-automation-recommender
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what…