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.
git 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/commands/boxlogodev/sapstack/sap-migo-debug)<a href="https://agentmods.dev/commands/boxlogodev/sapstack/sap-migo-debug"><img src="https://agentmods.dev/badge/commands/boxlogodev/sapstack/sap-migo-debug/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/boxlogodev/sapstack/sap-migo-debug"><img src="https://agentmods.dev/badge/commands/boxlogodev/sapstack/sap-migo-debug.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00965 |
| Opus 5.5 | $0.00000 | $0.00386 |
| Sonnet 5.5 | $0.00000 | $0.00193 |
| Haiku 4.5 | $0.00000 | $0.00097 |
Grade A, and why
sap-migo-debug 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 1mo 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
MIGO 디버그 파이프라인
입력: $ARGUMENTS
🎯 목표
MIGO 포스팅 실패 시 체계적으로 원인을 추적합니다. 한국 현장에서 흔한 패턴을 우선 점검합니다.
진단 순서
Step 1. 에러 메시지 파싱
- 사용자에게 전체 에러 메시지 (클래스.번호 형태) 요청
- 예:
M7 003— "Document XXX cannot be posted in period YYY" - 클래스별 해석 가이드:
- M7: MM 포스팅 일반
- F5: FI 계정 결정 / 기간
- ME: PO/계약 관련
- MEPO: PO 생성 관련
Step 2. 재고/가용성
- MMBE: 전체 재고 상황
- MB5B: 전기간 재고 이력 (음수 재고 탐지)
- MB52: 창고별 재고
- 체크:
- Negative stock 허용 여부 (OMJ1)
- Batch 관리 자재의 Batch 선택
- Serial Number 자재의 일련번호
Step 3. 이동 유형 설정
- OMJJ: 이동 유형 설정 확인
- OMWB: 계정 결정
- 체크:
- 이동 유형 101(GR) vs 103(GR Blocked Stock) vs 105(GR Release) 구분
- Special Stock indicator (E, K, Q 등)
- Reversal (102, 122) 시 원본 문서 추적
Step 4. 계정 결정 (OBYC)
- OBYC: Transaction Key 별 G/L 계정
- 흔한 원인:
- GBB-VBR 계정 누락
- WRX (GR/IR Clearing) 계정 누락
- BSX (Stock) 계정 누락
- 체크: MM 계정 그룹이 FI 회사코드와 매핑되었는지
Step 5. 기간 제어
- OMSY: MM 기간 (현 기간 + 전기간 2개월만 허용)
- OB52: FI 기간 vs MM 기간 일치 여부
- 한국 현장 이슈: MM 기간이 닫혔는데 FI만 열려 있는 경우 흔함
Step 6. 원가 / 가격
- MBEW: 자재 가격 레코드
- CKMLCP (S/4HANA): Actual Costing 실행 여부
- 체크:
- Moving Average Price (V) vs Standard Price (S)
- 가격 절대값이 0인 자재 — 포스팅 차단
- CO-PC 활성화 시 Costing Variant
Step 7. 한국 특화
- CVI KR 관련:
- 부가세 자동 분리 설정 (
J_1BNFE) - 전자세금계산서 발행 대상 플래그
- 부가세 자동 분리 설정 (
- 부가세 코드 매핑 (MWSKZ) 유효성
Step 8. 감사 흔적
- SE38 → RM07MDOC: 자재 문서 조회
- MB51: 자재 문서 리스트
- CDHDR/CDPOS: 변경 로그
- 한국 K-SOX — 이동 유형별 Dual Authorization 확인
📤 출력 형식
## 🔍 진단 결과
- 에러: (클래스.번호)
- 확률 높은 원인: (Top 3)
## 🛠 수정 단계
1. ...
2. ...
## 🛡 재발 방지
- ...
## 📖 관련 SAP Note
- (알려진 경우)
참조
plugins/sap-mm/skills/sap-mm/SKILL.mdplugins/sap-fi/skills/sap-fi/SKILL.md(계정 결정 이슈)agents/sap-fi-consultant.md(FI 측 깊은 분석 필요 시)
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.
- 1mo ago First seen · 96 lines · 0 tokens per session scan A 91b91e96763e
sap-migo-debug is a command published in the GitHub repository BoxLogoDev/sapstack (20 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 965 tokens. 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
check
Run the abap2UI5 gates (abaplint and the abap2UI5 linter) over the project or the changed classes, explain every finding and fix the ones that are clearly safe.
abap2ui5-check
Run the abap2UI5 gates (abaplint and the abap2UI5 linter) over the project or the changed classes, explain every finding and fix the ones that are clearly safe.
widget-validate
Validates SAC custom widget JSON metadata and JavaScript structure for correctness and best practices.
sac-debug
Debug SAC script issues with guided analysis and common error resolution.
sqlscript-validate
Validates SQLScript code for syntax, patterns, and best practices with auto-fix capability.
cap-troubleshooter
Diagnostic guide for common CAP errors and issues with solutions.