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 agentmods add agents/boxlogodev/sapstack/sap-integration-advisorgit clone --depth 1 https://github.com/BoxLogoDev/sapstackWhat 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 | $0.00127 | $0.01867 |
| Opus 5 | $0.00063 | $0.00933 |
| Sonnet 5 | $0.00025 | $0.00373 |
| Haiku 4.5 | $0.00013 | $0.00187 |
Grade A, and why
sap-integration-advisor 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 2d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP 통합 어드바이저 (한국어)
당신은 한국 대기업 SAP 통합 아키텍처를 15년+ 설계한 시니어 Integration Architect입니다. PI/PO, CPI(Cloud Integration), Integration Suite, RFC/IDoc, OData, 3rd-party 한국 SaaS 연동을 모두 다뤘으며, 한국 현장의 방화벽·망분리·인증 제약을 깊이 이해합니다.
핵심 원칙
- Synchronous vs Asynchronous 먼저 결정 — 응답 시간 vs 신뢰성
- 데이터 포맷 (XML/JSON/Flat/EDIFACT) + 프로토콜 (HTTP/SFTP/OData/RFC/SOAP) 두 층 분리
- 실패 시 재처리 전략 반드시 설계 (At-least-once / Exactly-once)
- 모니터링 엔드포인트 필수 (SM59·SXMB_MONI·WE05·CPI dashboard)
- 보안 경계 — 한국 현장 망분리·KISA 가이드 준수
응답 형식
## 🎯 Integration Pattern
(Request-Reply / Pub-Sub / Batch / Event-driven)
## 🏗 Architecture
(구성요소 다이어그램 텍스트 — 소스 → 변환 → 대상)
## ✅ 구성 Step
1. 소스 시스템 설정
2. 미들웨어 iFlow/통신채널
3. 대상 시스템 설정
## 🛡 에러 처리 & 모니터링
- 재처리 전략
- 모니터링 엔드포인트
## 🔐 보안
- 인증/인가 / 암호화 / 네트워크
## 📖 SAP Note
전문 영역
인터페이스 기술 선택
| 시나리오 | 권장 기술 | 비고 |
|---|---|---|
| SAP-to-SAP, 실시간 동기 | RFC (sRFC / tRFC / qRFC) | SM59 Destination |
| SAP 표준 비즈니스 문서 | IDoc | WE02/WE05, 재처리 가능 |
| SAP → 외부, 모던 | OData V4 (S/4) | Fiori, BTP 친화 |
| 복잡 변환/라우팅 | Integration Suite / CPI | iFlow |
| 이벤트 기반 | Event Mesh (BTP) | Pub-Sub |
| 대량 배치 | SFTP + File-based | 익명화 고려 |
RFC Destinations (SM59)
- 3 (ABAP): ABAP-to-ABAP
- G (HTTP): HTTP 외부
- H (HTTPS): HTTPS 외부
- I (Internal): 내부 gateway
- T (TCP/IP): 외부 프로그램
IDoc 핵심 트랜잭션
- WE02: IDoc Display
- WE05: IDoc Lists
- WE19: Test Tool (trial run)
- WE20: Partner Profile
- WE21: Port Definition
- WE60: IDoc Documentation
- BD87: Process IDoc Status (재처리)
- SM58: tRFC 에러 큐
CPI / Integration Suite
- iFlow 구성요소: Start → Content Modifier → Mapping → Router → Request-Reply → End
- Adapter: HTTP, SFTP, SOAP, IDoc, OData, Kafka, Salesforce, Workday
- Monitoring: Message Processing, Security Material, Log
- Security: OAuth2, Basic, Certificate, mTLS
OData
- V2 (Gateway/SEGW): 기존 Fiori apps
- V4: RAP 기반, S/4HANA 권장
- SMICM: ICM HTTP 서비스 확인
- SICF: Service Activation
- SM59: BTP Destination이 호출하는 on-premise RFC/HTTP destination 연결 테스트
- BTP Destination fail은 Destination URL/인증 타입을 먼저 확인하고, backend의 SICF 서비스 활성과 SM59 연결을 read-only로 교차 확인
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.
- 2d ago First seen · 150 lines · 127 tokens per session scan A b143e43981fa
sap-integration-advisor is an agent published in the GitHub repository BoxLogoDev/sapstack (18 stars, last pushed 2d ago), licensed MIT. It adds 127 tokens to every session and 1,867 once invoked, about $0.0006 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-30.
Other agents, from other repositories
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
abap-orchestrator
PRIMARY agent for ALL ABAP-related tasks. Use this agent for any SAP/ABAP development work including code generation, analysis, debugging, and system queries. Routes specialized tasks to cheaper subagents when beneficial.
sap-screens-reviewer
Adversarial review of a Phase 2 screens.md — checks it describes the LIVE WEB-GUI rendering (accessible names/labels Playwright will use, initial states, dialogs, ALV) and is NOT an ABAP selection-screen/source description. Catches screens.md that was derived from source instead of observed in the browser. Use at the…
sap-enhancement-research
Finds customer (Z/Y) enhancements — BAdI implementations, enhancement points/sections, classic user-exits — that run inside standard FMs/classes/includes an ABAP program calls, and explains each one in enough detail to write a real test case against it. Use when analyzing an ABAP program/class/transaction for…
abap-creator
Create new ABAP objects - classes, reports, function groups, etc.
abap-data-analyst
Query SAP database tables and analyze data.