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 vigneshbarani24/sap-superpowers --skill ewmgit 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/skills/vigneshbarani24/sap-superpowers/ewm)<a href="https://agentmods.dev/skills/vigneshbarani24/sap-superpowers/ewm"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/ewm/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/vigneshbarani24/sap-superpowers/ewm"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/ewm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.02629 |
| Opus 5 | $0.00028 | $0.01314 |
| Sonnet 5 | $0.00011 | $0.00526 |
| Haiku 4.5 | $0.00006 | $0.00263 |
Grade A, and why
ewm 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Extended Warehouse Management (EWM)
This skill enforces correct EWM implementation practices, ensuring that warehouse structure is designed before process configuration begins, RF device testing includes actual hardware validation, and warehouse processes are mapped to physical reality — not configured from templates disconnected from the warehouse floor.
Content Routing
| Topic | Section |
|---|---|
| Warehouse structure design | Warehouse Structure |
| Inbound/outbound processes | Inbound Process / Outbound Process |
| Wave management | Wave Management |
| Task and resource management | Task and Resource Management |
| RF framework | RF Framework |
| VAS and deconsolidation | Value-Added Services |
| Yard management | Yard Management |
| Embedded EWM | Embedded EWM in S/4HANA |
| Integration points | Integration Points |
Iron Laws
- ALWAYS DESIGN WAREHOUSE STRUCTURE BEFORE PROCESS CONFIGURATION. Storage types, sections, bins, activity areas, and work centers define the physical-to-logical mapping. Process configuration (putaway, picking, goods issue) depends entirely on this structure. Configuring processes without finalized structure means rework.
- NEVER SKIP RF DEVICE TESTING WITH ACTUAL HARDWARE. RF transactions behave differently on handheld scanners than on desktop emulators. Screen rendering, barcode scanning speed, network latency, and ergonomics MUST be validated on the actual devices warehouse workers will use. Emulator-only testing is not testing.
- NEVER CONFIGURE PUTAWAY STRATEGIES WITHOUT WAREHOUSE WALK-THROUGH. Putaway rules that look correct in SPRO fail when the warehouse has physical constraints — aisle widths, weight limits, temperature zones, forklift turning radius. Walk the floor before configuring.
- ALWAYS MAP PROCESS STEPS TO WAREHOUSE DOCUMENT FLOW. EWM documents (inbound delivery -> warehouse task -> warehouse order -> posting change) must be understood end-to-end. Configuring one step without understanding the full document flow creates process gaps.
- NEVER GO LIVE WITHOUT CYCLE COUNT STRATEGY. Inventory accuracy degrades from day one without systematic cycle counting. Configure cycle count strategy and bin status management before go-live, not after the first stock discrepancy.
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 · 268 lines · 55 tokens per session scan A 9fa3ee34b456
ewm is a skill published in the GitHub repository vigneshbarani24/sap-superpowers (9 stars, last pushed 18d ago), licensed MIT. It adds 55 tokens to every session and 2,629 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
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
slack-construct-agents
Standing context for Slack sibling agents — one room per team, creator-posted introductions, bot-to-bot hop discipline. Ships as instructions.md composed into the group's CLAUDE.md at spawn; there is no workflow to invoke.
equipment-fleet-manager
Manage construction equipment fleet. Track utilization, maintenance, and assignments.
sap-expert
Expert in SAP ERP systems, ABAP programming, SAP HANA, S/4HANA, Fiori applications, and SAP integration patterns including OData, RFC, and IDoc. Use when the user mentions ERP, enterprise, business apps, ABAP, HANA, or S/4HANA, or when the task involves SAP Ecosystem, ABAP Development, Integration Technologies, or…
tia-multiuser
TIA Portal Multiuser Engineering operations. Use for managing server projects, local sessions, and multiuser commissioning workflows.