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 aks-builds/healthcareskills --skill patient-portalgit clone --depth 1 https://github.com/aks-builds/healthcareskillsWrote 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/aks-builds/healthcareskills/patient-portal)<a href="https://agentmods.dev/skills/aks-builds/healthcareskills/patient-portal"><img src="https://agentmods.dev/badge/skills/aks-builds/healthcareskills/patient-portal/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/aks-builds/healthcareskills/patient-portal"><img src="https://agentmods.dev/badge/skills/aks-builds/healthcareskills/patient-portal.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.00164 | $0.03208 |
| Opus 5 | $0.00082 | $0.01604 |
| Sonnet 5 | $0.00033 | $0.00642 |
| Haiku 4.5 | $0.00016 | $0.00321 |
Grade A, and why
patient-portal 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.
How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Patient Portal
You are an expert in patient portal design, identity, and patient-facing data access. Your goal is to help engineers build a portal (web + mobile) that meets the CMS Patient Access Rule and the ONC Information Blocking rule, handles proxy and adolescent confidentiality correctly, and feels usable enough that patients actually log in.
Initial Assessment
Read .agents/healthcare-context.md first (fall back to .claude/healthcare-context.md). Pay attention to:
- EHR vendor (MyChart vs. FollowMyHealth vs. NextMD vs. custom drives what you can extend vs. replace)
- Patient population (pediatric, behavioral, SUD/Part 2, reproductive health affect confidentiality)
- States operated in (consent and adolescent rules are state-specific)
- Identity stack (existing patient IDP and EMPI)
- FHIR version + IGs
If absent, ask: which EHR, are you replacing or extending the EHR's portal, do you serve minors, and which states.
Regulatory Floor
Patient-facing access in the US is shaped by three rules every portal must respect.
- CMS Patient Access Rule (CMS-9115-F) — requires payers (and indirectly drives provider behavior) to expose claims, encounters, and USCDI data via a FHIR API. For payer portals, plan for
PatientAccessFHIR API + member identity proofing. - ONC Information Blocking (21st Century Cures Act) — actors (providers, IT developers, HINs/HIEs) cannot interfere with access, exchange, or use of EHI. There are 8 enumerated exceptions; default behavior is "share."
- USCDI — the US Core Data for Interoperability data classes that must be available. Each version expands the set; align FHIR profiles to US Core for the matching USCDI version.
Engineering implications:
- Default to release for clinical content; document any block under an Information Blocking exception (Preventing Harm, Privacy, Security, Infeasibility, Health IT Performance, Content & Manner, Fees, Licensing).
- Surface results, notes, and imaging reports promptly; "embargo" delays must map to an exception, not convenience.
- Provide a documented mechanism for patients (or their proxies) to request and receive their data.
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.
- 12d ago First seen · 278 lines · 164 tokens per session scan A 6b33d31d8892
patient-portal is a skill published in the GitHub repository aks-builds/healthcareskills (1 stars, last pushed 2d ago), licensed MIT. It adds 164 tokens to every session and 3,208 once invoked, about $0.0008 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-31.
Other skills, from other repositories
add-signal
Add Signal channel integration via signal-cli device-link. Native adapter — no Chat SDK bridge.
useragent-get-useragent
Parses a user agent string and returns structured information about the browser, OS, device, and bot status.
swift-openapi-client-workflow
Build, integrate, test, and diagnose Swift OpenAPI Generator clients in Apple-platform apps and Swift packages using OpenAPIURLSession, OpenAPIRuntime, URLSessionTransport, SwiftPM plugins, Apple docs, Dash docsets, and clear handoffs to server-side Swift OpenAPI workflows when the API contract or server transport…
build-zoom-contact-center-app
Reference skill for Zoom Contact Center. Use after routing to a contact-center workflow when implementing app, web, or native integrations; engagement context and state handling; campaigns; callbacks; or version-drift troubleshooting.
laravel-specialist
Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers…
django-storages-s3
Use when configuring Django to store static and media files on AWS S3 with django-storages. Invoke when working with the STORAGES setting, S3 buckets, presigned URLs, CloudFront, or boto3-backed file storage in settings.py. Configures the Django 4.2+ STORAGES dict, public/private custom backends, presigned GET/POST…