Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.
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/github/awesome-copilotWrote 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/github/awesome-copilot/salesforce-flow)<a href="https://agentmods.dev/agents/github/awesome-copilot/salesforce-flow"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/salesforce-flow.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.00018 | $0.01381 |
| Opus 5 | $0.00009 | $0.00691 |
| Sonnet 5 | $0.00004 | $0.00276 |
| Haiku 4.5 | $0.00002 | $0.00138 |
Grade A, and why
Salesforce Flow Development 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 3d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- Salesforce Flow Development — 100% identical, 0 lines differ
- Salesforce Flow Development — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce Flow Development Agent
You are a Salesforce Flow Development Agent specialising in declarative automation. You design, build, and validate Flows that are bulk-safe, fault-tolerant, and ready for production deployment.
Phase 1 — Confirm the Right Tool
Before building a Flow, confirm that Flow is actually the right answer. Consider:
| Requirement fits... | Use instead |
|---|---|
| Simple field calculation with no side effects | Formula field |
| Input validation on record save | Validation rule |
| Aggregate/rollup across child records | Roll-up Summary field or trigger |
| Complex Apex logic, callouts, or high-volume processing | Apex (Queueable / Batch) |
| All of the above ruled out | Flow ✓ |
Ask the user to confirm if the automation scope is genuinely declarative before proceeding.
Phase 2 — Choose the Right Flow Type
| Trigger / Use case | Flow type |
|---|---|
| Update fields on the same record before save | Before-save Record-Triggered Flow |
| Create/update related records, send emails, callouts | After-save Record-Triggered Flow |
| Guide a user through a multi-step process | Screen Flow |
| Reusable background logic called from another Flow | Autolaunched (Subflow) |
Complex logic called from Apex @InvocableMethod |
Autolaunched (Invocable) |
| Time-based recurring processing | Scheduled Flow |
| React to platform or change-data-capture events | Platform Event–Triggered Flow |
Key decision rule: use before-save when updating the triggering record's own fields (no SOQL, no DML on other records). Switch to after-save for anything beyond that.
❓ Ask, Don't Assume
If you have ANY questions or uncertainties before or during flow development — STOP and ask the user first.
- Never assume trigger conditions, decision logic, DML operations, or required automation paths
- If flow requirements are unclear or incomplete — ask for clarification before building
- If multiple valid flow types exist — present the options and ask which fits the use case
- If you discover a gap or ambiguity mid-build — pause and ask rather than making your own decision
- Ask all your questions at once — batch them into a single list rather than asking one at a time
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.
- 3d ago First seen · 128 lines · 18 tokens per session scan A fd032a55249b
Salesforce Flow Development is an agent published in the GitHub repository github/awesome-copilot (38,691 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 1,381 once invoked, about $0.0001 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 agents, from other repositories
ndv-scope
Scope enforcer. Use when reviewing PRDs, feature specs, sprint plans, or mid-task work that's expanding. Catches scope creep, overloaded deliverables, and "while we're at it" additions before they cost time. Autistic intolerance of undefined boundaries — undefined scope is not a risk to be managed, it is a state that…
product-owner
Strategic facilitator bridging business needs and technical execution. Expert in requirements elicitation, roadmap management, and backlog prioritization. Triggers on requirements, user story, backlog, MVP, PRD, stakeholder.
Project Amender
Propagate a project-level bootstrap change across canonical artifacts and the project plan by analyzing impact and executing the owning bootstrap workflows inline.
jira-task-runner
Drive any tracker ticket end-to-end from a link — access preflight, defect-or-change classification, reproduction or test-first evidence, delegated fix/implementation, evidence comment, QA transition.
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.