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 BoxLogoDev/sapstack --skill sap-cloudgit clone --depth 1 https://github.com/BoxLogoDev/sapstackWrote 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/boxlogodev/sapstack/sap-cloud)<a href="https://agentmods.dev/skills/boxlogodev/sapstack/sap-cloud"><img src="https://agentmods.dev/badge/skills/boxlogodev/sapstack/sap-cloud.svg" alt="Measured on agentmods" 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.00164 | $0.05509 |
| Opus 5 | $0.00082 | $0.02755 |
| Sonnet 5 | $0.00033 | $0.01102 |
| Haiku 4.5 | $0.00016 | $0.00551 |
Grade A, and why
sap-cloud 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 4d 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 — 549 lines — stays where its author put it; the contents beside it link to each section on GitHub.
1. Environment Intake Checklist
When any Cloud PE issue or extension task is reported, collect before answering:
- Cloud PE Version: 2401 / 2402 / 2403 / 2405 / (specific release month/year)
- Tenant Type: Production / Non-Production (Test / Staging)
- Extension Tier: Tier 1 (Key User Extensibility) / Tier 2 (Side-by-Side BTP) / Tier 3 (On-Stack ABAP Cloud)
- Deployment Model: Cloud PE (never mention on-premise SE38/SE80/SMOD/CMOD — they are forbidden)
- Industry Sector: Manufacturing / Finance / Retail / Public Sector / Other
- Change Control: Are you in Fit-to-Standard phase or Operations phase?
2. Clean Core Principles (Non-Negotiable)
SAP S/4HANA Cloud PE enforces Clean Core — no modifications to SAP standard code or tables.
| Activity | On-Premise (ECC/S/4HANA OP) | Cloud PE |
|---|---|---|
| ABAP Modifications (SE38) | ✓ Allowed | ✗ FORBIDDEN |
| Function Module Enhancements (SMOD/CMOD) | ✓ Allowed | ✗ FORBIDDEN |
| Workflow Customizing (SWDD) | ✓ Allowed | △ Limited (no code exits) |
| IMG Configuration | ✓ Full (SPRO) | △ Limited (Manage Your Solution) |
| BAdI Implementation | ✓ Standard (SE19) | ✗ FORBIDDEN (use RAP instead) |
| Enhancement Spots | ✓ Full (BADI_DEF) | ✗ FORBIDDEN |
| Standard Table Modifications | ✓ Allowed (append structures) | ✗ FORBIDDEN |
| Transport Mechanism | ✓ TMS (TP/TP4) | ✗ Direct upload to Cloud ALM |
Forbidden T-codes in Cloud PE:
- SE11 (ABAP Dictionary modifications)
- SE38 (Classic ABAP program creation)
- SE80 (Object Navigator for custom code)
- SMOD / CMOD (Exit/Enhancement modification)
- SWDD (Classic Workflow definition)
- SPAM / SAINT (Transport/patch — managed by SAP)
3. Key User Extensibility — Tier 1 (Self-Service)
3.1 Custom Fields (Extensibility Add-Ons)
Enable end users (non-developers) to add business fields without coding.
How to Create Custom Fields:
- In Cloud PE UI → Manage Your Solution → Custom Fields
- Select object (Purchase Order, Sales Order, Material Master, etc.)
- Click Create Custom Field
- Field Name:
ZZ_CUSTOM_FIELD(naming convention) - Data Type: Quantity / Amount / Date / Text / Dropdown
- Label: Business-facing label (Korean: "사용자정의 필드")
- Field Name:
- Deploy: Activation is immediate (no transport)
- UI Integration: Auto-added to relevant screens (Fiori UIs)
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/best-practices/governance.md 2.4 KB
- references/best-practices/operational.md 11 KB
- references/best-practices/period-end.md 2.0 KB
- references/de/quick-guide-de.md 2.3 KB
- references/en/quick-guide-en.md 2.2 KB
- references/img/fit-to-standard.md 15 KB
- references/img/key-user-extensibility.md 13 KB
- references/img/overview.md 8.3 KB
- references/ja/quick-guide-ja.md 2.3 KB
- references/ko/quick-guide.md 2.2 KB
- references/ko/SKILL-ko.md 351 B
- references/vi/quick-guide-vi.md 2.4 KB
- references/zh/quick-guide-zh.md 2.0 KB
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.
- 4d ago First seen · 549 lines · 164 tokens per session scan A ea66687dfc4d
sap-cloud is a skill published in the GitHub repository BoxLogoDev/sapstack (18 stars, last pushed 8d ago), licensed MIT. It adds 164 tokens to every session and 5,509 once invoked, about $0.0008 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-04.
Other skills, from other repositories
sap-btp-best-practices
SAP BTP best practices for enterprise architecture, account management, security, and operations, with verification evidence tracked in the repository ledger. Use when planning BTP implementations, setting up account hierarchies, configuring environments, implementing authentication, designing CI/CD pipelines…
sap-btp-cloud-logging
This skill provides comprehensive guidance for SAP Cloud Logging service on SAP BTP. Use when setting up Cloud Logging instances, configuring log ingestion from Cloud Foundry or Kyma runtimes, implementing OpenTelemetry observability, analyzing logs/metrics/traces in OpenSearch Dashboards, configuring SAML…
sap-btp-cloud-platform
Comprehensive SAP Business Technology Platform (BTP) reference for cloud development, deployment, and operations. Use when setting up BTP accounts, working with Cloud Foundry environment, deploying to Kyma (Kubernetes, serverless), developing in ABAP environment (RAP, CDS), managing entitlements and quotas…
sap-btp-cloud-transport-management
Comprehensive skill for SAP Cloud Transport Management service on SAP BTP. Use when setting up transport landscapes, configuring transport nodes and routes, managing import queues, deploying MTAs across Cloud Foundry environments, integrating with CI/CD pipelines, configuring ABAP environment transports…
sap-btp-developer-guide
Develops business applications on SAP Business Technology Platform (BTP) using CAP (Node.js/Java) or ABAP Cloud. Use when: building cloud applications on SAP BTP, deploying to Cloud Foundry or Kyma runtimes, integrating with SAP HANA Cloud, implementing SAP Fiori UIs, connecting to remote SAP systems, building…
sap-btp-integration-suite
Enterprise integration solutions using SAP Integration Suite on BTP. Covers Cloud Integration (iFlows), API Management, Event Mesh, Edge Integration Cell, Integration Advisor, Trading Partner Management, and Migration Assessment. Use for building integration flows, managing API proxies, event-driven architectures…