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 approval-processesgit 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/approval-processes)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/approval-processes"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/approval-processes/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/approval-processes"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/approval-processes.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.00063 | $0.01590 |
| Opus 5 | $0.00032 | $0.00795 |
| Sonnet 5 | $0.00013 | $0.00318 |
| Haiku 4.5 | $0.00006 | $0.00159 |
Grade A, and why
approval-processes 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 7d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Salesforce Admin expert in approval workflow design. Your goal is to build approval paths that are clear to submitters, reliable for approvers, and simple enough to operate without turning every business exception into a broken locked record.
Before Starting
Check for salesforce-context.md in the project root. If present, read it first.
Only ask for information not already covered there.
Gather if not available:
- What object is being approved, and what event should trigger submission?
- Who approves: named users, managers, lookup fields, or queues via custom logic?
- Should the record lock during approval, and who still needs edit access?
- Does the process need recall, re-submit, delegation, or mobile/email approval?
- Is this really a standard Approval Process, or is it multi-object workflow that belongs in Flow/custom objects?
How This Skill Works
Mode 1: Build from Scratch
Use this for a new approval requirement.
- Confirm the process deserves approval at all - many "approvals" are really notifications or task routing.
- Choose the pattern with the matrix below.
- Define entry criteria tightly so only approval-worthy records can be submitted.
- Define approver source explicitly and what happens if it is blank.
- Define submission, approval, rejection, and recall outcomes before building the first step.
- Test locked-record behavior with real submitter and approver personas, not just as SysAdmin.
Mode 2: Review Existing
Use this for inherited approval processes or orgs with approval sprawl.
- Check entry criteria for over-submission or duplicate submission paths.
- Check whether steps still reflect the real org structure and approver ownership.
- Check what actions fire on submit, approve, reject, and recall - especially field updates and emails.
- Check whether record locking blocks legitimate admin or business operations.
- Check whether the process should be replaced by Flow or a custom approval object because the logic outgrew standard approvals.
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.
- 7d ago First seen · 133 lines · 63 tokens per session scan A 9627a011155b
approval-processes is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,590 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
approval-processes
Design, review, or troubleshoot Salesforce Approval Processes. Triggers: 'submit for approval', 'approver', 'record locked', 'recall approval', 'approval step', 'discount approval'. NOT for submitting or acting on approvals from Apex - use admin/approval-process-apex-patterns. NOT for CPQ Advanced Approvals (SBAA…
integration-rule-engine
A declarative routing engine that turns ticket / error attributes (reporter, label, project, area path, error class, environment) into a tag + AI agent + priority assignment, so cross-source workflows ("security tickets always go to the OWASP reviewer") stay out of code and in user-editable rules.
pipefy-building
Thin router for Pipefy build and configure asks: map user intent to the correct domain skill (pipes, automations, AI agents, iPaaS, portals, etc.). Use when the user wants to create, build, configure, or integrate something in Pipefy and you need to know which skill to open. Do not use this skill as a delivery…
company-handbook
The cross-director coordination protocol for the 1ai business kingdom. Defines how Content, Video, Image, Marketing, and Sales directors work together. Has memory via 1ai-hub brain, follows 1ai-rules, and coordinates with Vilona (GM). Use when coordinating multiple directors, resolving conflicts between teams, or when…
setup-platform-development
Help set up the platform development policy — contribution mode, governance, and sharing.
do
Alias for /brana:backlog start with freeform text. Routes to the best skill or creates a task. Use /brana:backlog start directly for the same behavior.