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 client-onboarding-designgit 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/client-onboarding-design)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/client-onboarding-design"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/client-onboarding-design/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/client-onboarding-design"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/client-onboarding-design.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.00089 | $0.03211 |
| Opus 5 | $0.00044 | $0.01605 |
| Sonnet 5 | $0.00018 | $0.00642 |
| Haiku 4.5 | $0.00009 | $0.00321 |
Grade A, and why
client-onboarding-design 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client Onboarding Design
This skill activates when a practitioner needs to design the end-to-end FSC client onboarding process — mapping document collection touchpoints, sequencing compliance checkpoints, defining approval steps, and specifying welcome journey handoffs before any platform configuration begins. It does NOT cover Action Plan template configuration mechanics (see fsc-action-plans), OmniStudio component implementation details, or Flow builder construction.
Before Starting
Gather this context before working on anything in this domain:
- Confirm whether OmniStudio is licensed in the org. OmniStudio FlexCards and OmniScripts are a separately licensed add-on — they are not included with the base FSC license. If OmniStudio is not licensed, standard Screen Flows are the native fallback for guided intake. Do not assume OmniStudio availability without checking the org's installed packages and license entitlements.
- Identify the compliance and regulatory requirements that govern sequencing. In financial services, certain steps are legally mandatory in a specific order (e.g., KYC identity verification before account funding, consent capture before any data processing). These constraints drive the entire workflow structure and cannot be compromised for UX convenience.
- Understand the template versioning constraint before designing process governance. Action Plan templates — the primary task execution mechanism — cannot be edited after activation. Publishing a revised process requires a clone-and-republish workflow. This constraint must be designed into governance from day one: who owns template versioning, how changes are requested, and how in-flight onboarding journeys are handled during a version transition.
- Establish the anchor record for onboarding. In FSC, the process typically centers on a FinancialAccount or Account record. Clarifying the anchor object determines which Action Plan template types can be used and how the welcome journey trigger is configured.
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 · 183 lines · 89 tokens per session scan A 3bcd0346b251
client-onboarding-design is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 89 tokens to every session and 3,211 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
client-onboarding-design
Use this skill when designing the FSC client onboarding process — mapping document collection touchpoints, approval steps, compliance checkpoint sequencing, and welcome journey handoffs. Trigger keywords: client onboarding design, onboarding workflow requirements, document collection flow, compliance checkpoint…
vendor-review
Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.
entity-compliance
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity…
integration-management
Post-closing M&A integration tracker — phased workplan, consent tracking, contract assignment at scale, weekly status reports. Initializes from whatever deal artifacts are available (purchase agreement, deal summary, closing checklist) and connects to deal-context.md and closing-checklist.yaml from the M&A cold-start.…
matter-workspace
Manage matter workspaces — new, list, switch, close, or detach (practice-level). File-management logic for keeping one client or engagement's context separate from every other. Use when working across multiple clients or matters, when the user says "new matter", "switch matter", "list matters", "close matter", or when…
patent-docket
A workflow coordinator for patent case files, from an inventor's technical disclosure to patent application documents. A patent docket is the tracked record of a patent matter, including its stage, questions, drafts, and handoffs.