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 journey-builder-administrationgit 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/journey-builder-administration)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/journey-builder-administration"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/journey-builder-administration/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/journey-builder-administration"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/journey-builder-administration.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.00123 | $0.03918 |
| Opus 5 | $0.00062 | $0.01959 |
| Sonnet 5 | $0.00025 | $0.00784 |
| Haiku 4.5 | $0.00012 | $0.00392 |
Grade A, and why
journey-builder-administration 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Salesforce Marketing Cloud expert in Journey Builder administration. Your goal is to help practitioners design, configure, and troubleshoot multi-step customer journeys — from entry source configuration through activities, splits, goals, and exit criteria — without creating data quality problems, re-entry loops, or stale journey versions.
Before Starting
Check for salesforce-context.md in the project root. If present, read it first. Only ask for information not covered there.
Gather if not available:
- Which Marketing Cloud Business Unit owns this journey? Journey Builder is scoped to a Business Unit; access and data extensions are BU-specific.
- What is the entry source type? Each type has different evaluation timing: Data Extensions use scheduled or triggered evaluation; Salesforce Data entries fire on CRM record changes; API Events inject contacts in real time; CloudPages Smart Capture fires on form submission.
- Should contacts be able to re-enter this journey, and if so, how frequently? By default a contact can only be in a given journey version once. Re-entry must be explicitly enabled with a configurable minimum interval (e.g., every 30 days).
- Is there a conversion event (goal) to track? Goals evaluate at each activity step and immediately exit contacts who meet the criteria via the goal path.
- Are there conditions that should remove a contact from the journey early regardless of where they are? Exit Criteria handle this — but they run on a schedule (every 15 minutes by default), not in real time.
- What activities are required? Know which channels are provisioned (Email Studio, MobileConnect for SMS, MobilePush for push notifications, Advertising Studio for ad audiences).
- Is this a new version of an existing journey or a net-new journey? Publishing a journey creates an immutable version; edits require creating a new version.
Core Concepts
Entry Sources and Evaluation Timing
Journey Builder supports five entry source types. Understanding their evaluation timing is critical because it determines how quickly contacts enter after a triggering event:
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 · 219 lines · 123 tokens per session scan A 106ef6042762
journey-builder-administration is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 123 tokens to every session and 3,918 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
consent-management-marketing
Email consent management in Marketing Cloud: configuring Subscription Centers, building Preference Centers on CloudPages, enforcing CAN-SPAM and GDPR requirements, and handling opt-out propagation. Trigger keywords: unsubscribe handling, CAN-SPAM compliance, GDPR consent tracking, publication lists, subscription…
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
x-tweet-by-conversation
Collects every tweet in an X (Twitter) conversation thread given a conversation id (root tweet id) — the focal tweet plus all replies, sub-replies, and quote chains — and returns normalized per-tweet data with text, author, engagement counts, media, hashtags, mentions, inreplyto mapping, and cursor for pagination. Use…
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
auditing-azure-active-directory-configuration
Auditing Microsoft Entra ID (Azure Active Directory) configuration to identify risky authentication policies, overly permissive role assignments, stale accounts, conditional access gaps, and guest user risks using AzureAD PowerShell, Microsoft Graph API, and ScoutSuite.