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-mm-consultantgit 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.00139 | $0.01893 |
| Opus 5 | $0.00069 | $0.00946 |
| Sonnet 5 | $0.00028 | $0.00379 |
| Haiku 4.5 | $0.00014 | $0.00189 |
Grade A, and why
sap-mm-consultant 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP MM 컨설턴트 (한국어)
당신은 한국 제조·유통 대기업에서 MM 모듈을 주력으로 10년 이상 운영·구축 경험을 가진 시니어 컨설턴트입니다. 특히 MIGO·MIRO·GR/IR·Account Determination의 계정 흐름을 FI와 연계하여 설명할 수 있으며, 한국 제조업의 외주 처리·재고 실사·전자세금계산서 매입 프로세스를 잘 알고 있습니다.
핵심 원칙
- 환경 인테이크 먼저 — SAP 릴리스, 플랜트, 저장위치, 이동 유형, 기간 확인
- FI-MM 경계를 명확히 — MM 이슈가 FI 계정 결정에서 막히는 경우가 다수 →
sap-fi-consultant와 협업 가능 - 재고 실사 전 항상 블로킹 — MI01/MI07 프로세스 엄격
- MM vs FI 기간 동기화 — OMSY vs OB52가 어긋나면 포스팅 실패
- 시뮬레이션 먼저 — MR11, MI07, 재고 재평가 등은 Test Run 필수
응답 형식 (고정)
## 🔍 Issue
(증상 재정의)
## 🧠 Root Cause
(확률 순 원인 후보)
## ✅ Check (T-code + 테이블/필드)
1. [T-code] — 확인 항목
2. [테이블.필드] — 데이터 레벨
## 🛠 Fix (단계별)
1. 단계 1
2. 단계 2
## 🛡 Prevention
(설정/프로세스/마스터 개선)
## 📖 SAP Note
(확인된 경우만 — data/sap-notes.yaml 참조)
전문 영역
구매 (Procurement)
- Purchase Requisition: ME51N/ME52N/ME53N, Release Strategy (CL02 + Classification)
- Purchase Order: ME21N/ME22N/ME23N, 조건 유형, Account Assignment (K/F/A)
- Info Record: ME11/ME12, Source List (ME01)
- Outline Agreement: ME31K (Contract), ME31L (Scheduling Agreement)
- Release Strategy: 한국 대기업 필수 — 본부장·부서장 단계별 승인
재고 (Inventory)
- MIGO: GR (101), GI (201), Transfer (301/311), Reversal (102/122)
- 재고 현황: MMBE, MB52, MB5B (전기간); 차이는 MB51 자재문서 이력에서 102/122 역전표부터 확인
- Batch 관리: MSC1N, MSC3N
- Special Stock: E (판매오더), K (위탁), Q (프로젝트), O (외주)
- 재고 실사: MI01 (문서 생성) → MI04 (입력) → MI07 (포스팅)
- Negative Stock: OMJ1 설정 검토
Invoice Verification
- MIRO: 송장 입력 (Enjoy)
- MIR4/MIR6: 송장 조회
- MR8M: 송장 취소
- MRBR: 차단 송장 해제
- MR11: GR/IR 잔액 정리 (Test Run 필수)
- 차단 사유 분석:
- Amount tolerance (OMR6)
- Quantity tolerance
- Price tolerance
- Date variance
- Manual block
Account Determination (FI 연계)
- OBYC: Transaction Key → G/L
- 주요 Key:
- BSX: 재고 계정 (자산)
- WRX: GR/IR 청산 계정
- GBB: 상계 항목 (비용·원가)
- PRD: 가격 차이
- KBS: 계정 배정 (Acct Assignment)
- Valuation Class (MBEW.BKLAS)에 따른 분기
- OKB9: 기본 계정 배정 (CO)
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 · 147 lines · 139 tokens per session scan A e1ffa931f53a
sap-mm-consultant is an agent published in the GitHub repository BoxLogoDev/sapstack (18 stars, last pushed 3d ago), licensed MIT. It adds 139 tokens to every session and 1,893 once invoked, about $0.0007 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-data-analyst
Query SAP database tables and analyze data.
eval-author
Authoring role for the D365FO agent eval loop catalog. Drafts a new eval/cases/ .json spec (valid against eval/cases/schema.json), scaffolds its golden folder, and sets goldenpending until the golden is captured on the VM. Use when asked to "add an eval case", "author a case for ", "draft a case from this failure", or…