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/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/commands/banibratachatterjee/awesomesalesforceskills/automation-migration-router)<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/automation-migration-router"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/automation-migration-router/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/automation-migration-router"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/automation-migration-router.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.00577 |
| Opus 5 | $0.00000 | $0.00289 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
automation-migration-router 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/migrate-automation
Invoke the automation-migration-router agent. Wave 3a of the redesign (see plan file).
Synopsis
/migrate-automation --source-type <wf_rule|process_builder|approval_process|auto>
--object <ApiName>
--target-org <alias>
[--mode analyze|plan|migrate]
[--consolidation-mode aggressive|conservative|auto]
[--include-inactive]
[--time-dependent-handling scheduled-path|defer-to-scheduled-flow|refuse]
[--canary-percent N]
[--parallel-run-days N]
What it does
Routes one of four source automation types into the matching migration dispatch, returning an inventory, target design (Flow or Orchestrator), parallel-run validation plan, and rollback plan. See agents/automation-migration-router/AGENT.md for the full contract.
Legacy alias commands
These four aliases invoke the same router with a preset --source-type and emit a one-line deprecation notice. They ship until the removal window declared in docs/MIGRATION.md (Wave 7).
| Alias | Equivalent to |
|---|---|
/migrate-wfr-to-flow |
/migrate-automation --source-type wf_rule ... |
/migrate-pb-to-flow |
/migrate-automation --source-type process_builder ... |
/migrate-workflow-pb |
/migrate-automation --source-type auto ... |
/migrate-approval-to-orchestrator |
/migrate-automation --source-type approval_process ... |
Safety
- The router never activates / deactivates / deploys — output is a markdown plan.
- Refusal codes are canonical (
agents/_shared/REFUSAL_CODES.md). - The citation gate enforces that every skill / template / decision-tree cited resolves to a real file.
See also
agents/_shared/harnesses/migration_router/decision_table.md— source-type dispatch tableagents/_shared/harnesses/migration_router/phase_gates.md— shared parallel-run + rollbackstandards/decision-trees/automation-selection.md— Flow vs Apex vs Orchestrator vs Agentforce upstream decision
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 501ed6047dfe
automation-migration-router 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 577 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.