Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkillsnpx agentmods add commands/banibratachatterjee/awesomesalesforceskills/migrate-approval-to-orchestratorWrote 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/commands/banibratachatterjee/awesomesalesforceskills/migrate-approval-to-orchestrator)<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/migrate-approval-to-orchestrator"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/migrate-approval-to-orchestrator/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/commands/banibratachatterjee/awesomesalesforceskills/migrate-approval-to-orchestrator"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/migrate-approval-to-orchestrator.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.00000 | $0.00441 |
| Opus 5 | $0.00000 | $0.00220 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
migrate-approval-to-orchestrator 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 12d 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.
What it actually says
/migrate-approval-to-orchestrator — LEGACY ALIAS (Wave 3a)
Deprecation notice: this command is now an alias. It invokes the
automation-migration-routerwith--source-type=approval_processand emits this deprecation notice. Switch to the canonical/migrate-automationform at your convenience; the alias ships until the removal window declared indocs/MIGRATION.md(Wave 7).
Canonical form
/migrate-automation --source-type approval_process [--object <ApiName>] --target-org <alias>
Alias behavior
Running /migrate-approval-to-orchestrator <args> is equivalent to:
/migrate-automation --source-type approval_process <args>
The approval-specific migration gate — deciding whether each approval
process should become a Flow Orchestration, stay as-is, route to
Agentforce, migrate with caveats, or retire — is preserved verbatim in
the router's
decision_table.md
under the approval_process row. The canary-population parallel-run
pattern (vs the shadow-field pattern used for Flow-target migrations)
lives in
phase_gates.md.
Why the change
Wave 3a of the redesign consolidated four migrators into one router. See
agents/_shared/harnesses/migration_router/README.md
for the rationale.
See also
/migrate-automation— canonical router entry pointagents/automation-migration-router/AGENT.md— router contractdocs/MIGRATION.md— removal timeline (authored in Wave 7)
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.
- 12d ago First seen · 45 lines · 0 tokens per session scan A f25bf3784873
migrate-approval-to-orchestrator is a command published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 441 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.