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-ibp-forecast-debug)<a href="https://agentmods.dev/commands/boxlogodev/sapstack/sap-ibp-forecast-debug"><img src="https://agentmods.dev/badge/commands/boxlogodev/sapstack/sap-ibp-forecast-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-ibp-forecast-debug"><img src="https://agentmods.dev/badge/commands/boxlogodev/sapstack/sap-ibp-forecast-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.00039 | $0.00741 |
| Opus 5.5 | $0.00016 | $0.00296 |
| Sonnet 5.5 | $0.00008 | $0.00148 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
sap-ibp-forecast-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
/sap-ibp-forecast-debug — IBP 수요 예측 디버그
사용 시점
- 통계 예측 (Statistical Forecast)이 생성 안 됨
- 예측이 비현실적 (음수/0/극단치)
- 시즌성/추세가 안 잡힘
- Auto-ML 알고리즘 선택 이상
진단 체크리스트
Step 1: Planning Operator 확인
- IBP Web UI → Configuration → Planning Areas → [Your PA]
- Operators 탭 → Forecast Operator 정의
- 다음 확인:
- Operator 활성?
- Input/Output Key Figure 매핑 정확?
- Time horizon (n weeks/months)?
- Forecast Model 어떤 거?
Step 2: Forecast Model 점검
- Models → [Your Forecast Profile]
- 다음 확인:
- 알고리즘 적합? (Croston for intermittent, Triple ES for seasonal+trend)
- 파라미터 (alpha, beta, gamma) 적절?
- Horizon ≥ History/3 권장
- Outlier detection 활성?
Step 3: 히스토리 데이터
- Planning View에서 History Key Figure 확인
- 다음 확인:
- 최소 12-24 주기 히스토리 확보?
- 결측치 (gap) 있나? (있으면 0으로 처리됐는지 vs 매핑 실패)
- 단위 일관성? (단가 변경, 단위 변경)
Step 4: 마스터 매핑
- Master Data → Product / Location / Customer 확인
- 다음 확인:
- Planning Object 정의된 조합 (e.g., Product × Location) 활성?
- 매핑 깨진 객체 없음? (S/4 ↔ IBP)
Step 5: 실행 로그
- Application Jobs → 최근 Forecast Run
- 다음 확인:
- 상태: Success / Warning / Failed?
- 실행 시간 평소 대비?
- 처리한 Combination 수?
- Warning 메시지 (예: "no history", "model degenerate")?
흔한 원인
| 원인 | 증상 | 해결 |
|---|---|---|
| History 부족 | 0 또는 NaN 예측 | 최소 12 주기 보장 |
| Outlier | 폭발적 예측 | Outlier detection 활성 |
| 매핑 오류 | 일부 조합 누락 | External Codes 재매핑 |
| Operator 비활성 | 예측 안 생성 | Operator activate |
| Time profile 불일치 | period shift | Time profile 정합성 |
Output 형식 (Quick Advisory mode)
### Issue
[증상 요약]
### Root Cause
[원인]
### Check (T-code/UI + Field)
- Planning Area: ...
- Operator: ...
- ...
### Fix (Steps)
1. ...
2. ...
### Prevention
- ...
### SAP Note (if known)
- ...
복잡한 경우 (가설 2+ 가능) → /sap-session-start 호출.
참조
plugins/sap-ibp/skills/sap-ibp/SKILL.mdagents/sap-ibp-consultant.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.
- 1mo ago First seen · 95 lines · 39 tokens per session scan A 954cee144a7b
sap-ibp-forecast-debug is a command published in the GitHub repository BoxLogoDev/sapstack (20 stars, last pushed 23d ago), licensed MIT. It adds 39 tokens to every session and 741 once invoked, about $0.0002 per session on Opus 5.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
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.