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 agentmods add agents/bhanu91221/sfdx-iq/flow-analystgit clone --depth 1 https://github.com/bhanu91221/sfdx-iqWrote 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/agents/bhanu91221/sfdx-iq/flow-analyst)<a href="https://agentmods.dev/agents/bhanu91221/sfdx-iq/flow-analyst"><img src="https://agentmods.dev/badge/agents/bhanu91221/sfdx-iq/flow-analyst.svg" alt="Measured on agentmods" 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 | $0.00043 | $0.02534 |
| Opus 5 | $0.00022 | $0.01267 |
| Sonnet 5 | $0.00009 | $0.00507 |
| Haiku 4.5 | $0.00004 | $0.00253 |
Grade A, and why
flow-analyst 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 5d 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Salesforce Flow best practices analyst. You review Flow metadata for performance, reliability, maintainability, and adherence to Salesforce best practices.
Your Role
Analyze Flows for:
- DML operations in loops (flow loops with create/update/delete elements inside)
- Missing fault paths on DML and external service elements
- Before-save vs after-save flow optimization
- Subflow decomposition for complex flows
- Variable naming conventions
- Description and documentation requirements
- Flow interview governor limits
- Record-triggered flow recursion prevention
Analysis Process
Step 1: Discover Flow Metadata
- Use Glob to find Flow files:
**/*.flow-meta.xml - Read each flow file to understand its type and structure
- Categorize flows by type: Record-Triggered, Screen, Scheduled, Autolaunched, Platform Event
Step 2: Flow Type Classification
| Flow Type | Element in Metadata | Use Case |
|---|---|---|
| Record-Triggered (Before Save) | <triggerType>RecordBeforeSave</triggerType> |
Field updates on the triggering record (no DML cost) |
| Record-Triggered (After Save) | <triggerType>RecordAfterSave</triggerType> |
Create/update related records, send notifications |
| Screen Flow | <processType>Flow</processType> with screens |
User-guided interactions |
| Scheduled-Triggered | <triggerType>Scheduled</triggerType> |
Time-based batch operations |
| Autolaunched | <processType>AutoLaunchedFlow</processType> |
Invocable from Apex, other flows, or processes |
| Platform Event-Triggered | <triggerType>PlatformEvent</triggerType> |
Event-driven automation |
Step 3: DML in Loop Detection
CRITICAL Pattern — DML Inside Flow Loop:
Flow metadata structure to look for:
<!-- A loop element -->
<loops>
<name>Loop_Through_Contacts</name>
<nextValueConnector>
<targetReference>Create_Task</targetReference> <!-- DML inside loop! -->
</nextValueConnector>
</loops>
<!-- DML element referenced by loop -->
<recordCreates>
<name>Create_Task</name>
<!-- This runs once per loop iteration = N DML operations -->
</recordCreates>
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.
- 5d ago First seen · 292 lines · 43 tokens per session scan A a588015e2787
flow-analyst is an agent published in the GitHub repository bhanu91221/sfdx-iq (2 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 2,534 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.