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/vigneshbarani24/sap-superpowersWrote 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/vigneshbarani24/sap-superpowers/sap-migrate)<a href="https://agentmods.dev/commands/vigneshbarani24/sap-superpowers/sap-migrate"><img src="https://agentmods.dev/badge/commands/vigneshbarani24/sap-superpowers/sap-migrate.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.00038 | $0.00757 |
| Opus 5 | $0.00019 | $0.00378 |
| Sonnet 5 | $0.00008 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
sap-migrate 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 8d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sap-migrate
Invokes the sap-migration-analyzer agent with the s4hana-migration skill to assess a system or landscape for S/4HANA readiness. Evaluates conversion approach options, custom code exposure, simplification item impact, and data migration complexity. Blocks conclusions until evidence is collected — no assessment is made from memory alone.
Usage
/sap-migrate [system/landscape info]
Arguments:
[system/landscape info]— Describe the current landscape: ECC version, active modules, custom code volume, database, hosting model, and any known constraints. If you have a custom code analysis output or simplification item list, paste or reference it.
Examples:
/sap-migrate ECC 6.0 EHP8, Oracle DB, FI CO MM SD PP, ~3,000 custom objects, on-premise/sap-migrate SAP ECC 6.0 on HANA, EU data residency required, 500 custom programs, RISE with SAP target/sap-migrate Paste output of custom code analysis report here
What Happens
- The
sap-migration-analyzeragent is dispatched with thes4hana-migrationskill active. - The skill enforces a structured assessment process — conversion approach cannot be recommended before custom code and simplification item data is reviewed.
- The agent evaluates three conversion approaches: Greenfield (new implementation), Brownfield (system conversion), and Selective Data Transition (SDT) — and scores each against the provided context.
- Custom code impact is analyzed: deprecated APIs, non-released objects, removed tables, and compatibility packs required.
- Simplification items relevant to the active modules are identified and rated by impact.
- Data migration complexity is assessed: volume, quality, legacy structure, and tool recommendations (LTMC, LTMOM, BODS, Migration Cockpit).
- A risk-rated migration assessment is produced with a recommended path and next steps.
Output
A Migration Assessment document containing:
| Section | Content |
|---|---|
| Landscape Summary | Current system details, versions, modules, custom code volume |
| Conversion Approach | Greenfield / Brownfield / SDT scored and recommended with rationale |
| Custom Code Impact | Breakdown by category — critical, needs rework, compatible, deprecated |
| Simplification Items | Relevant items by module with impact rating and recommended action |
| Data Migration | Volume assessment, quality risks, recommended tooling |
| Timeline Estimate | Phase-by-phase effort range based on complexity |
| Risk Register | Top risks with probability, impact, and mitigation |
| Recommended Next Steps | Prioritized action list to begin migration planning |
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.
- 8d ago First seen · 62 lines · 38 tokens per session scan A ef10778559b8
sap-migrate is a command published in the GitHub repository vigneshbarani24/sap-superpowers (9 stars, last pushed 16d ago), licensed MIT. It adds 38 tokens to every session and 757 once invoked, about $0.0002 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-08-31.
Other commands, from other repositories
datasphere-cli
SAP Datasphere CLI command reference with examples.
datasphere-mcp-tools
List all available SAP Datasphere MCP tools with descriptions and usage examples.
widget-validate
Validates SAC custom widget JSON metadata and JavaScript structure for correctness and best practices.
seamless-planning-guide
Quick guidance on implementing Seamless Planning with SAP Datasphere.
cap-setup-wizard
Interactive guide for setting up new CAP projects with framework and database selection.
sac-planning-checklist
Generate a comprehensive checklist for SAC planning implementation projects.