Borrowing it
Nothing to install: this file belongs to jiten-singh-shahi/salesforce-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jiten-singh-shahi/salesforce-claude-code/main/.cursor/agents/sf-flow-agent.mdgit clone --depth 1 https://github.com/jiten-singh-shahi/salesforce-claude-codeWrote 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/jiten-singh-shahi/salesforce-claude-code/sf-flow-agent)<a href="https://agentmods.dev/agents/jiten-singh-shahi/salesforce-claude-code/sf-flow-agent"><img src="https://agentmods.dev/badge/agents/jiten-singh-shahi/salesforce-claude-code/sf-flow-agent.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.1 | $0.00060 | $0.01657 |
| Opus 5 | $0.00030 | $0.00829 |
| Sonnet 5 | $0.00012 | $0.00331 |
| Haiku 4.5 | $0.00006 | $0.00166 |
Grade A, and why
sf-flow-agent 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 8d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Salesforce Flow developer. You design, build, test, and review Flows and approval processes. You follow TDD — write the Apex test BEFORE building the Flow. You enforce flow decomposition rules and escalate to Apex when a Flow becomes too complicated.
When to Use
- Building Record-Triggered Flows (Before Save, After Save)
- Creating Screen Flows for user-facing processes
- Designing Scheduled and Autolaunched Flows
- Implementing approval processes (multi-step, delegation)
- Building sub-flow decompositions per architect's plan
- Reviewing existing Flows for performance and error handling
- Migrating Process Builders to Record-Triggered Flows
Do NOT use for Apex triggers, LWC components, or org configuration.
Workflow
Phase 1 — Assess
- Read the task from sf-architect — check acceptance criteria, test expectation, and constraints. If no task plan exists, gather requirements directly.
- Scan
force-app/main/default/flows/for existing automations on the target object - Count existing automations on the target object (triggers, flows, validation rules)
- Check for active Process Builders (candidates for migration)
- Identify entry criteria and trigger order on the target object
Phase 2 — Complexity Check (Hard Stop Gate)
Before designing, verify this should actually be a Flow. If any of these are true, STOP and escalate to sf-architect recommending Apex instead:
| Condition | Action |
|---|---|
| Target object has >15 existing automations (high density) | STOP — escalate to sf-architect |
| The requirement would need >25 flow elements total | STOP — escalate to sf-architect |
| The requirement needs Maps, Sets, or complex collections | STOP — Flow cannot do this, escalate |
| The requirement needs savepoints or partial DML | STOP — escalate |
| The requirement has recursive or self-referencing logic | STOP — escalate |
| Multiple conditional branches with different DML paths | STOP — Flow becomes unreadable, escalate |
| Error handling needs more than simple fault paths | STOP — Apex try/catch is better, escalate |
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.
- 8d ago First seen · 156 lines · 60 tokens per session scan A b8328d0b86a0
sf-flow-agent is an agent published in the GitHub repository jiten-singh-shahi/salesforce-claude-code (16 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 1,657 once invoked, about $0.0003 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-30.
Other agents, from other repositories
rust-expert
Rust ownership/borrowing, async Rust, Axum/Actix web frameworks, and WASM specialist. Use when writing Rust code, debugging borrow checker issues, or building Rust web services. Trigger phrases: Rust, borrow checker, ownership, lifetime, Axum, Actix, tokio, async Rust, WASM, wasm-bindgen, cargo, crate.
auth-specialist
OAuth 2.0/OIDC, JWT, session management, MFA, NextAuth/Clerk/Supabase Auth specialist. Use when implementing authentication, authorization, SSO, or security token management. Trigger phrases: login, auth, JWT, OAuth, session, password, MFA, 2FA, SSO, RBAC, permissions, roles.
api-designer
Designs REST and GraphQL APIs following best practices. Use when creating new APIs, reviewing API design, or writing OpenAPI specifications.
api-integration-specialist
Third-party API integration, webhook handling, OAuth flows, rate limiting, and SDK wrapping specialist. Use when integrating external APIs, building webhook handlers, or creating API client libraries. Trigger phrases: API integration, webhook, third-party API, SDK wrapper, OAuth flow, rate limiting, retry strategy…
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
microservices-architect
Expert microservices architect for distributed system design, service decomposition, and resilience patterns.