A planner for Salesforce Flow automations, where Flow is Salesforce’s tool for carrying out actions from business rules. It chooses a Flow type and lays out its elements, subflows, error handling, and tests.

Use it to plan record-triggered, scheduled, screen, or background Flows. It can include bulk-processing notes, a test matrix, and optionally a Flow XML skeleton.

It turns a plain-language requirement into a structured automation design and checks whether Flow is the right tool compared with Apex code or Agentforce. This helps expose volume and error-handling issues before implementation.

build-flow — Command for Claude Code by BanibrataChatterjee

Install

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.

Clone the repo

git clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkills

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/build-flow/github.svg)](https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/build-flow)

Your own site

<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/build-flow"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/build-flow/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/build-flow"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/build-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 554 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.00554
Opus 5.5	$0.00000	$0.00222
Sonnet 5.5	$0.00000	$0.00111
Haiku 4.5	$0.00000	$0.00055

Measured 2mo ago against content hash 73d0bfc86e1e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

build-flow 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 2mo 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.

commands/build-flow.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/build-flow — Design a Flow (any type) from a business requirement

Wraps agents/flow-builder/AGENT.md. Returns the Flow type decision, element plan, subflow plan, fault path, bulkification notes, and test matrix.

Step 1 — Collect inputs

Ask the user:

1. Requirement (plain English, one or two sentences)?
   Example: "When a Case is created on a Platinum-tier Account, route to the Platinum Support queue and notify the account owner"

2. Target object (if implied by the requirement)?
   Example: Case

3. Target org alias (required — agent checks for existing automation)?

4. Trigger context (optional)?
   before-save / after-save / scheduled / screen / autolaunched
   (Inferred from the requirement if omitted)

5. Expected volume (optional)?
   small / medium / high (drives bulkification emphasis)

6. Include the Flow XML skeleton in the output? yes / no
   (Default: no — design doc only)

Step 2 — Load the agent

Read agents/flow-builder/AGENT.md + mandatory reads, especially standards/decision-trees/automation-selection.md (the Flow-vs-Apex-vs-Agentforce gate).

Step 3 — Execute the plan

Run the automation-selection decision tree — may route to a different tool entirely
Probe for existing automation (list_flows_on_object, tooling_query on ApexTrigger)
Decompose into elements
Subflow plan
Bulkification review
Test design
Emit the design

Step 4 — Deliver the output

Summary (Flow type chosen + confidence)
Element plan (table)
Subflow plan
Fault path
Bulkification notes
Test matrix
XML skeleton (only if requested)
Process Observations
Citations

/analyze-flow (existing Wave-1 agent) after the flow is deployed
/gen-tests (existing) for any invocable Apex the flow calls
/scan-security (existing) if the flow does callouts
/audit-validation-rules if the agent flagged VR-vs-flow conflicts

Read the full file on GitHub · 80 lines

Changes

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.

2mo ago First seen · 80 lines · 0 tokens per session scan A 73d0bfc86e1e

Subscribe to this mod's changes

build-flow is a command published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (4 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 554 tokens. 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.

Planning

build-flow next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
build-flowBanibrataChatterjee/AwesomeSalesforceSkills	Command	4	6mo ago	Apache-2.0	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	today	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	today	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	today	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	today	MIT	A	14	Claude Code