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/analyze-flow)<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/analyze-flow"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/analyze-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.
<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/analyze-flow"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/analyze-flow.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.00480 |
| Opus 5 | $0.00000 | $0.00240 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
analyze-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 10d 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.
What it actually says
/analyze-flow — Flow vs Apex routing + bulkification review
Wraps agents/flow-analyzer/AGENT.md. For a Flow or an sObject, routes via standards/decision-trees/automation-selection.md, checks bulkification, and flags trigger/flow co-existence risks.
Step 1 — Collect inputs
Ask:
1. Either a Flow path or an sObject API name?
Example flow path: force-app/main/default/flows/Lead_AutoConvert.flow-meta.xml
Example object: Lead
2. Target-org alias? (optional — enables list_flows_on_object)
If the user gave a flow path, skip the object question. If they gave an object, scan force-app/main/default/flows/ for matching flows.
Step 2 — Load the agent
Read agents/flow-analyzer/AGENT.md fully + the automation decision tree + flow skills listed in Mandatory Reads.
Step 3 — Execute
Follow the 5-step plan:
- Gather flows in scope (local + optional org-side via
list_flows_on_object) - Apply the automation decision tree to each flow (KEEP / FIX_IN_PLACE / MIGRATE_TO_APEX / MIGRATE_TO_AGENTFORCE)
- Bulkification checks (DML/SOQL in loops, missing fault paths, untyped collections)
- Co-existence check (trigger + flow on same event)
- Recommendations with specific element changes
Step 4 — Deliver
- Summary with verdict distribution
- Per-flow report (verdict, decision-tree branch, findings, fixes)
- Co-existence section if triggers + flows overlap
- Citations
Step 5 — Recommend follow-ups
/consolidate-triggersif co-existence is flagged and Apex should own the event./refactor-apexif a flow should migrate to Apex — applied to the new handler./request-skillif a flow pattern has no canonical skill.
What this command does NOT do
- Does not modify the flow XML.
- Does not activate or deactivate flows in the org.
- Does not pass judgment on Flow vs Apex outside the decision tree.
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.
- 10d ago First seen · 62 lines · 0 tokens per session scan A f13792282f70
analyze-flow 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 480 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
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.