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 BanibrataChatterjee/AwesomeSalesforceSkills --skill health-cloud-patient-setupgit clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkillsWrote 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/banibratachatterjee/awesomesalesforceskills/health-cloud-patient-setup)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/health-cloud-patient-setup"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/health-cloud-patient-setup/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/banibratachatterjee/awesomesalesforceskills/health-cloud-patient-setup"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/health-cloud-patient-setup.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.00092 | $0.02964 |
| Opus 5 | $0.00046 | $0.01482 |
| Sonnet 5 | $0.00018 | $0.00593 |
| Haiku 4.5 | $0.00009 | $0.00296 |
Grade A, and why
health-cloud-patient-setup 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Health Cloud Patient Setup
This skill activates when a practitioner needs to configure patient or member records in Salesforce Health Cloud — covering Person Account enablement, Health Cloud-specific patient record type creation, care team role setup, and patient card customization for clinical data display. It is NOT for standard Salesforce account setup or general person account tasks outside the Health Cloud context.
Before Starting
Gather this context before working on anything in this domain:
- Confirm Health Cloud managed package is installed (package namespace
HealthCloudGA). Person Account enablement is a prerequisite, but it is also an org-wide, irreversible operation. Never enable in production without a full impact assessment. - Determine whether Person Accounts are already enabled. If they are, skip that step entirely — attempting to re-enable causes no change but wastes time and can be confusing.
- Identify the record types needed: Health Cloud typically requires at minimum a "Patient" (or "Member") person account record type alongside any existing business account record types. Understand what page layouts and profiles will be affected.
- Clarify what clinical data the org consumes: FHIR/HL7 data flows through dedicated Health Cloud objects (EhrPatientMedication, PatientHealthCondition, PatientImmunization, etc.) — it does not map to standard Contact or Account fields.
- Understand whether a care team is required and what roles exist (e.g., Primary Care Physician, Care Manager, Social Worker). Care team roles are configured in Health Cloud settings, not through standard role hierarchies.
Core Concepts
Person Accounts: Org-Wide, Irreversible Prerequisite
Health Cloud patients are represented as Person Accounts — a Salesforce platform feature that merges Account and Contact into a single record for individual people. Enabling Person Accounts is a permanent, org-wide change. Once enabled, every Account record gains an IsPersonAccount boolean field and the object model changes globally: person account records have no associated Contact record (the Contact fields are embedded on the Account). This cannot be reversed by Salesforce Support. All integrations, reports, SOQL queries, and third-party tools that assume standard Account/Contact separation must be reviewed and updated after enablement.
What ships with it
7 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 · 188 lines · 92 tokens per session scan A ebae65369e00
health-cloud-patient-setup is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 92 tokens to every session and 2,964 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
care-plan-configuration
Configure care plan templates, problems, goals, and tasks in Salesforce Health Cloud - the Integrated Care Management (ICM) model (Spring '23+, FHIR R4-aligned) and the legacy CarePlanTemplatec + Case Tasks model. Trigger keywords: care plan template, ICM care plan, PGI library, action plan template, problem…
care-coordination-requirements
Use this skill when mapping care coordination process requirements for Health Cloud: designing care team workflows, transition of care handoffs, social determinants of health (SDOH) barrier tracking, and care gap identification. NOT for building care plan templates, problems, and goals — use…
care-program-management
Configure or troubleshoot Health Cloud Care Programs: CareProgram hierarchy, patient enrollment (CareProgramEnrollee), consent prerequisites, program products (CareProgramEnrolleeProduct), provider associations (CareProgramProvider). Trigger keywords: care program, program enrollment, enrollee, program product…
clinical-data-requirements
Use this skill when defining clinical data model requirements for Health Cloud: HL7/FHIR data mapping, interoperability requirements, FHIR R4-aligned object activation, CodeableConcept constraints, and middleware translation requirements. NOT for the field-level mapping work itself — use data/fhir-data-mapping. NOT…
antd
Use when the user's task involves Ant Design (antd) — writing antd components, debugging antd issues, querying antd APIs/props/tokens/demos, migrating between antd versions, or analyzing antd usage in a project. Triggers on antd-related code, imports from 'antd', or explicit antd questions.
v3-create-crud
A page generator for standard create, read, update, and delete screens, commonly called CRUD screens. It uses Element Plus, a Vue user-interface library, to build tables, searches, pagination, forms, and delete confirmations.