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-deliver)<a href="https://agentmods.dev/commands/vigneshbarani24/sap-superpowers/sap-deliver"><img src="https://agentmods.dev/badge/commands/vigneshbarani24/sap-superpowers/sap-deliver/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/vigneshbarani24/sap-superpowers/sap-deliver"><img src="https://agentmods.dev/badge/commands/vigneshbarani24/sap-superpowers/sap-deliver.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.00028 | $0.00536 |
| Opus 5.5 | $0.00011 | $0.00214 |
| Sonnet 5.5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
sap-deliver 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 1mo 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
/sap-deliver
Runs the SAP Delivery Factory for a specified SAP Activate phase.
Usage
/sap-deliver <phase> [--industry <name>] [--country <name>] [--modules <list>]
Phases
| Phase | Deliverables | Description |
|---|---|---|
discover |
5 | Project charter, stakeholder map, requirements, risks, scope |
prepare |
5 | Estimation, architecture, change management, business case, plan |
explore |
6 | Fit/gap, process designs, functional specs, migration, testing, integration |
realize |
6 | Technical specs, code, unit tests, code review, SIT, training |
deploy |
5 | Data migration, cutover, go-live readiness, UAT, transport release |
run |
5 | Hypercare, status reports, value realization, lessons learned, knowledge transfer |
status |
— | Show current project delivery status across all phases |
Examples
/sap-deliver discover
/sap-deliver prepare --industry retail --country germany --modules SD,MM,FI
/sap-deliver status
/sap-deliver explore
What It Does
- Loads project context (industry, country, SAP version, in-scope modules)
- Invokes the
delivery-factoryskill for the specified phase - Chains the required skills in dependency order
- Dispatches agents in parallel where possible
- Produces all phase deliverables with quality scores
- Reports phase status
Output
Creates a deliverables/ directory in the project with phase-organized artifacts:
deliverables/
├── discover/
│ ├── project-charter.md
│ ├── stakeholder-raci.md
│ ├── requirements.md
│ ├── risk-register.md
│ └── scope-definition.md
├── prepare/
│ ├── effort-estimate.md
│ ├── solution-architecture.md
│ ├── change-management-plan.md
│ ├── business-case.md
│ └── project-plan.md
└── factory-status.md
Skill Chain
This command invokes: delivery-factory → which orchestrates all phase-specific skills.
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.
- 1mo ago First seen · 68 lines · 28 tokens per session scan A 6503a330e2f4
sap-deliver is a command published in the GitHub repository vigneshbarani24/sap-superpowers (10 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 536 once invoked, about $0.0001 per session on Opus 5.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
add-ai
Add an AI / LLM feature to an existing abap2UI5 app - a chat or a summarize-this-data panel, on a local provider first, then on a real model through the samples-stack LLM classes, with secrets kept out of the code.
check
Run the abap2UI5 gates (abaplint and the abap2UI5 linter) over the project or the changed classes, explain every finding and fix the ones that are clearly safe.
find-sample
Search the three abap2UI5 sample catalogues (samples, samples-controls, samples-stack) and show the best three matches with class, what it shows and a link.
abap2ui5-find-sample
Search the three abap2UI5 sample catalogues (samples, samples-controls, samples-stack) and show the best three matches with class, what it shows and a link.
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.