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-integration-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-integration-cloud)<a href="https://agentmods.dev/skills/boxlogodev/sapstack/sap-integration-cloud"><img src="https://agentmods.dev/badge/skills/boxlogodev/sapstack/sap-integration-cloud.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.00157 | $0.11596 |
| Opus 5 | $0.00078 | $0.05798 |
| Sonnet 5 | $0.00031 | $0.02319 |
| Haiku 4.5 | $0.00016 | $0.01160 |
Grade A, and why
sap-integration-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 3d 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 — 930 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sap-integration-cloud — Integration Suite + Datasphere
1. Environment Intake Checklist
- Integration scope — CPI (Cloud Platform Integration) / Datasphere / API Mgmt / Event Mesh?
- Source/Target — S/4 (Cloud/OnPrem) / SuccessFactors / Ariba / 3rd party?
- Protocol — REST / SOAP / OData / IDoc / SFTP / JDBC?
- Authentication — OAuth / Basic / Certificate / SAML?
- Specific issue — iFlow design, error handling, perf, certificate, monitoring?
Also collect these before proposing a fix:
- SAP source release — ECC 6.0 EhP or S/4HANA release year.
- Deployment — On-Premise, RISE/Private Cloud, or S/4HANA Cloud Public Edition.
- Industry and data class — finance, HR, health, trade, or other regulated data.
- BTP landscape — region, subaccount, Cloud Foundry environment, dev/test/prod tenant.
- Artifact identity — package, iFlow name, deployed version, last transport/change time.
- Failure window — first failure time with timezone, frequency, last successful message.
- Correlation evidence — sanitized MPL Message ID and business correlation key.
- Contract — sender/receiver schema version, Content-Type, encoding, cardinality rules.
- Endpoint — destination alias, Cloud Connector location ID, receiver service and timeout.
- Security — authentication type and certificate/secret expiry date, never the secret itself.
- Business impact — delayed, missing, duplicated, or incorrectly transformed documents.
- Replay risk — whether the receiver is idempotent and who approves business reprocessing.
Do not wait for perfect intake before helping. If context is missing, label the diagnosis provisional and provide only read-only evidence checks.
1.1 Evidence privacy contract
- Never request or reproduce a production payload containing 주민등록번호, 계좌, 급여, 건강정보, 이메일, 전화번호, access token, client secret, or private key.
- Request only field names, schema fragments without values, redacted error text, counts, timestamps, hashes, message status, and correlation IDs.
- Replace business identifiers consistently so one sanitized message can still be correlated across CPI, PI/PO, and ECC/S/4.
- Treat CPI Trace and attachment logging as temporary data collection. Use a bounded window, minimum users, and the approved retention/deletion process.
- If a payload sample is essential, reproduce the structure with synthetic data in a lower tenant.
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.0 KB
- references/best-practices/operational.md 1.6 KB
- references/best-practices/period-end.md 1.6 KB
- references/de/quick-guide-de.md 3.4 KB
- references/en/quick-guide-en.md 3.3 KB
- references/img/connectivity-security.md 2.2 KB
- references/img/cpi-iflow-setup.md 2.1 KB
- references/img/datasphere-replication.md 2.1 KB
- references/img/overview.md 1.4 KB
- references/ja/quick-guide-ja.md 3.6 KB
- references/ko/quick-guide.md 3.6 KB
- references/vi/quick-guide-vi.md 3.8 KB
- references/zh/quick-guide-zh.md 3.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.
- 3d ago First seen · 930 lines · 157 tokens per session scan A 3f057537202d
sap-integration-cloud is a skill published in the GitHub repository BoxLogoDev/sapstack (18 stars, last pushed 7d ago), licensed MIT. It adds 157 tokens to every session and 11,596 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-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…
sap-abap
Comprehensive ABAP development skill for SAP systems. Use when writing ABAP code, working with internal tables, structures, ABAP SQL, object-oriented programming, RAP (RESTful Application Programming Model), CDS views, EML statements, ABAP Cloud development, string processing, dynamic programming, RTTI/RTTC, field…
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…
sap-cap-capire
SAP Cloud Application Programming Model (CAP) development skill using Capire documentation. Use when: building CAP applications, defining CDS models, implementing services, working with SAP HANA/SQLite/PostgreSQL databases, deploying to SAP BTP Cloud Foundry or Kyma, implementing Fiori UIs, handling authorization…
sap-sqlscript
This skill should be used when the user asks to "write a SQLScript procedure", "create HANA stored procedure", "implement AMDP method", "optimize SQLScript performance", "handle SQLScript exceptions", "debug HANA procedure", "create table function", "inspect a browser-based Datasphere SQL editor with Microsoft Edge…