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 skills add BanibrataChatterjee/AwesomeSalesforceSkills --skill flow-for-adminsgit 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/skills/banibratachatterjee/awesomesalesforceskills/flow-for-admins)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/flow-for-admins"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/flow-for-admins/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/skills/banibratachatterjee/awesomesalesforceskills/flow-for-admins"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/flow-for-admins.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.00068 | $0.02388 |
| Opus 5 | $0.00034 | $0.01194 |
| Sonnet 5 | $0.00014 | $0.00478 |
| Haiku 4.5 | $0.00007 | $0.00239 |
Grade A, and why
flow-for-admins 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 9d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Salesforce Admin expert in automation. Your goal is to design Flows that are bulkified, fault-tolerant, maintainable, and correctly scoped to the right flow type — and to help debug Flows that are failing in production.
Before Starting
Check for salesforce-context.md in the project root. If present, read it first — particularly CI/CD pipeline details (Flow deployments require special handling) and whether Process Builder or Workflow Rules are being migrated.
Only ask for information not already covered there.
Gather if not available:
- What trigger type? (Record save, user click, schedule, external event)
- What object? What's the approximate record volume?
- Is this replacing an existing automation? (Workflow Rule, Process Builder, old Flow)
- Are any callouts or integrations involved?
How This Skill Works
Mode 1: Build from Scratch
User has a requirement. Goal: select the right flow type and design a correct structure.
- Clarify the trigger: what causes this automation to run?
- Select flow type using the decision matrix below
- Identify: entry criteria, required variables, DML operations, callouts
- Design fault paths for every operation that can fail
- Plan bulkification: does this work for 200 records at once?
- Document: use the flow design template (templates/flow-design-template.md)
Mode 2: Review Existing
User shares a Flow or describes its structure. Goal: find issues before they hit production.
- Check for fault connectors on every Get, Create, Update, Delete, and callout element
- Check for record-triggered flow anti-patterns (SOQL in loops, DML on unrelated objects)
- Check variable naming (no
variable1, descriptive names) - Check entry criteria — is the flow running more often than needed?
- Check version management — are old versions deactivated?
- Check error handling — does the fault path do something useful (email admin, log, rollback)?
Mode 3: Troubleshoot
User has a Flow error — either from an email notification or a user report.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 186 lines · 68 tokens per session scan A 5d525808765d
flow-for-admins is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 68 tokens to every session and 2,388 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-09-03.
Other skills, from other repositories
clash-resolution-analyzer
Analyze BIM clash detection results and suggest resolutions. Prioritize clashes, identify patterns, assign responsibility, and track resolution status.
bugherd-automation
Automate Bugherd tasks via Rube MCP (Composio). Always search tools first for current schemas.
feedback-workflow
A command-line workflow for reading and responding to approved software feedback. It keeps track of the feedback version, approval, work claim, evidence, and result.
incident-learning
Convert operational incident and near-miss evidence into durable product, engineering, test, evaluation, and governance improvements with verified closure. Separate observed facts from causal hypotheses and unresolved uncertainty; map follow-up work across code, tests, skills, operations, product, and governance…
shepherd-start
Open a focused investigation session for one bug: pull its full tracker detail, load past lessons and triage history, and produce an investigation plan. Use when starting work on a single ticket, after /shepherd-sync has built the backlog.
incident-triage
Use telemetry, activity, boards, and hierarchy together when debugging live operational issues.