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 commands/boxlogodev/sapstack/sap-master-data-checkgit 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.00054 | $0.00729 |
| Opus 5 | $0.00027 | $0.00365 |
| Sonnet 5 | $0.00011 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
sap-master-data-check 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.
What it actually says
SAP 마스터데이터 사전검증
입력: $ARGUMENTS
목표
기간마감 전에 마스터데이터의 필수 필드 누락, 비활성 마스터, 중복 등록을 사전에 점검하여 마감 시 발생할 수 있는 오류를 예방합니다.
안전 규칙
- 마스터데이터 조회만 수행 — 변경 권장 시 사용자 확인 필수
- 회사코드·조직 단위 값은 사용자가 제공
실행 절차
Step 1 — 환경 확인
사용자에게 다음을 질문:
- 검증 대상 (vendor / customer / material / equipment / all)
- 회사코드 (BUKRS)
- SAP 릴리스 (ECC / S/4HANA)
Step 2 — 검증 규칙 로드
data/master-data-rules.yaml 참조하여 대상 마스터 유형의 필수 필드 목록 제시.
Step 3 — 검증 안내
각 마스터 유형별:
공급업체 (Vendor/BP)
- 통제계정 (LFB1-AKONT) 설정 여부
- 지급조건 (LFB1-ZTERM) 설정 여부
- 지급방법 (LFB1-ZWELS) 설정 여부
- 은행 정보 (LFBK) 등록 여부
- 사업자등록번호 (한국 필수)
- 조회 T-code: FK03 / XK03 / BP (S/4)
고객 (Customer/BP)
- 통제계정 (KNB1-AKONT) 설정 여부
- 판매영역 뷰 (KNVV) 완성 여부
- 여신한도 (KNKK-KLIMK / UKM) 설정 여부
- 조회 T-code: FD03 / XD03 / BP (S/4)
자재 (Material)
- 기본단위 (MARA-MEINS) 설정 여부
- 가격제어 (MBEW-VPRSV) 설정 여부
- 평가클래스 (MBEW-BKLAS) 설정 여부
- MRP 유형 (MARC-DISMM) 설정 여부 (생산 자재)
- 조회 T-code: MM03
장비 (Equipment)
- 원가센터 (EQUI-KOSTL) 할당 여부
- 기능위치 (EQUI-TPLNR) 할당 여부
- 조회 T-code: IE03
Step 4 — 결과 보고
검증 결과를 severity별로 분류:
- Error (마감 차단): 즉시 수정 필요
- Warning (경고): 검토 후 판단
위임
- FI 마스터 → sap-fi-consultant
- MM 마스터 → sap-mm-consultant
- SD 마스터 → sap-sd-consultant
- PM 마스터 → sap-pm-consultant
참조
data/master-data-rules.yamldocs/best-practices/master-data-governance.md
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 · 71 lines · 0 tokens per session scan A cba32081ac27
sap-master-data-check is a command published in the GitHub repository BoxLogoDev/sapstack (18 stars, last pushed 3d ago), licensed MIT. It adds 54 tokens to every session and 729 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-08-30.
Other commands, from other repositories
exact-omzet
Omzet per klant per maand uit Exact Online.
exact-balans
Balans / grootboeksaldi uit Exact Online.
exact-openstaande-debiteuren
Toon de openstaande debiteuren uit Exact Online.
exact-ouderdomsanalyse
Ouderdomsanalyse openstaande debiteuren uit Exact Online.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.