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 care-plan-configurationgit 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/care-plan-configuration)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/care-plan-configuration"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/care-plan-configuration/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/care-plan-configuration"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/care-plan-configuration.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.00125 | $0.03677 |
| Opus 5 | $0.00063 | $0.01839 |
| Sonnet 5 | $0.00025 | $0.00735 |
| Haiku 4.5 | $0.00013 | $0.00368 |
Grade A, and why
care-plan-configuration 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Care Plan Configuration
This skill activates when a practitioner needs to configure care plan templates, problems, goals, or tasks in Salesforce Health Cloud. It covers both the Integrated Care Management (ICM) model — the FHIR R4-aligned, platform-native architecture introduced in Spring '23 and the target of all future Salesforce investment — and the legacy managed-package model based on CarePlanTemplate__c and Case Tasks. The skill provides decision guidance on which model to use, prerequisite setup steps (including PGI library), and template configuration procedures. It is NOT for general case management, clinical program enrollment, or non-Health-Cloud task frameworks.
Before Starting
Gather this context before working on anything in this domain:
- Determine which care plan architecture the org uses. The two models share no object schema — using advice intended for one model in an org running the other will produce configuration that does not work. Check for the presence of
CarePlanTemplate__crecords (legacy) orActionPlanTemplate+ProblemDefinitionrecords (ICM). - If the org intends to use ICM, confirm whether the PGI (Problem/Goal/Intervention) library has been set up. The PGI library is a prerequisite for ICM care plan templates to reference standardized problems and goals. Skipping this step is the single most common ICM configuration failure.
- Understand the org's investment horizon. Salesforce has publicly stated that the legacy managed-package care plan model (CarePlanTemplate__c + Case Tasks) receives no future investment. New implementations should target ICM. Existing legacy implementations should plan migration.
- Identify which Health Cloud permission sets are assigned to care coordinator and care manager profiles. Both models require specific permission sets beyond HealthCloudFoundation for care plan creation and access.
- Confirm Health Cloud managed package version. ICM features are available from Spring '23 onwards; orgs on older package versions cannot use the ICM model without upgrading.
What ships with it
6 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 · 204 lines · 125 tokens per session scan A 100d08cdce49
care-plan-configuration is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 125 tokens to every session and 3,677 once invoked, about $0.0006 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…
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.
hunt-django
Hunt Django-specific vulnerabilities: DRF permission gaps, ORM injection, and admin exploitation.