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.
git 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/commands/banibratachatterjee/awesomesalesforceskills/design-flow-orchestrator)<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/design-flow-orchestrator"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/design-flow-orchestrator/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/commands/banibratachatterjee/awesomesalesforceskills/design-flow-orchestrator"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/design-flow-orchestrator.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.00000 | $0.00501 |
| Opus 5 | $0.00000 | $0.00251 |
| Sonnet 5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
design-flow-orchestrator 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 12d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design-flow-orchestrator — Design or audit a Flow Orchestration
Wraps agents/flow-orchestrator-designer/AGENT.md. Produces stages, steps, work-item assignees, interactive/background step mix, transition criteria, and restart/recall behavior.
Step 1 — Collect inputs
Ask the user:
1. Mode? design | audit
2. Target org alias (required — agent probes existing Orchestrations + referenced subflows)?
3. Workflow description (for design)?
Example: "3-stage contract review with legal, procurement, and customer sign-off"
4. Assignees per stage? (user | group | queue | formula-driven)
5. Restart / recall requirements?
6. SLA per stage (if any)?
If the description has fewer than 2 stages, STOP — this is a single Flow, not an Orchestration.
Step 2 — Load the agent
Read agents/flow-orchestrator-designer/AGENT.md + mandatory reads (flow/orchestration-flows, flow/subflows-and-reusability, flow/screen-flows).
Step 3 — Execute the plan
- Classify as Flow vs Orchestration (per standards/decision-trees/automation-selection.md).
- Decompose into stages.
- For each stage: steps, assignees, interactive/background mix, transitions.
- Map each step to an existing subflow or a new one.
- Emit restart/recall + cancellation semantics.
Step 4 — Deliver the output
- Summary + confidence
- Stage/step diagram (mermaid)
- Per-step assignee + type
- Subflow mapping
- Restart/recall/cancellation behavior
- Audit findings (inactive stages, orphaned subflows, missing fault paths)
- Process Observations
- Citations
Step 5 — Recommend follow-ups
/build-flowfor each subflow that doesn't yet exist/analyze-flowon the referenced subflows before deploying/architect-permsif orchestration runs as different user contexts
What this command does NOT do
- Does not deploy Orchestrations.
- Does not build the screen flows / subflows referenced.
- Does not replace BPM platforms — flags when the requirement outgrows Orchestration.
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.
- 12d ago First seen · 72 lines · 0 tokens per session scan A 6c7aead89c86
design-flow-orchestrator is a command published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 501 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.