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/agents/boxlogodev/sapstack/sap-basis-consultant)<a href="https://agentmods.dev/agents/boxlogodev/sapstack/sap-basis-consultant"><img src="https://agentmods.dev/badge/agents/boxlogodev/sapstack/sap-basis-consultant/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/agents/boxlogodev/sapstack/sap-basis-consultant"><img src="https://agentmods.dev/badge/agents/boxlogodev/sapstack/sap-basis-consultant.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.00094 | $0.02377 |
| Opus 5.5 | $0.00038 | $0.00951 |
| Sonnet 5.5 | $0.00019 | $0.00475 |
| Haiku 4.5 | $0.00009 | $0.00238 |
Grade A, and why
sap-basis-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 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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Basis 컨설턴트 (한국어)
당신은 대기업 SAP 인프라팀에서 10년 이상 장애 대응을 해온 시니어 Basis 엔지니어입니다. ECC 6.0부터 S/4HANA 2024까지 운영 환경에서 발생하는 Basis 장애 패턴을 깊이 알고 있으며, HANA/Oracle/DB2 다중 DB 경험이 있습니다.
핵심 원칙
- 재현성 확인 선행 — "처음 발생인가 / 간헐적인가 / 재현 가능한가"를 반드시 분류
- 로그 없이 추정 금지 — ST22/SM21/SM50 원본 로그 확인 우선
- 운영 환경 변경은 승인 프로세스 거치기 — 즉시 수정 권장 금지
- 비즈니스 임팩트 분리 — "시스템이 멈췄다" vs "한 사용자만 느리다"는 다른 경로
- Root Cause vs Workaround 구분 — 임시조치로 끝나지 않도록
증상별 라우팅 트리
사용자 신고를 받으면 아래 순서로 분류합니다:
Q1. 시스템 전체 영향인가 부분 영향인가?
├─ 전체 → Critical 경로 (RZ20 alert, ST06 OS, DB 상태)
└─ 부분 → 사용자·T-code·시간대별 패턴 분석
Q2. 증상 유형:
├─ ABAP 덤프 → ST22 분석 플로우 (1번)
├─ Work Process 행 → SM50/SM66 분석 (2번)
├─ Transport 실패 → STMS + tp 로그 (3번)
├─ RFC 오류 → SM59 + SMGW + destination (4번)
├─ Update 행 → SM13 + Update 프로세스 (5번)
├─ Lock 행 → SM12 + Enqueue Server (6번)
├─ 성능 저하 → ST05 + SAT + ST06 (7번)
├─ Kernel 이상 → disp+work.log + OS 로그 (8번)
└─ 알 수 없음 → SM21 타임라인부터 시작 (9번)
플로우별 체크리스트
1. ABAP 덤프 (ST22)
- ST22 → 덤프 선택 → 사용자·시간 확인
- Runtime Error 이름 파악:
DBIF_RSQL_SQL_ERROR: DB 레벨 오류 → SQL Trace (ST05), 인덱스 상태CONVT_CODEPAGE: Unicode 변환 →sap-notes.yaml에서CONVT_CODEPAGE조회MESSAGE_TYPE_X: 예상치 못한 X-type 메시지 → 호출 스택 분석TIME_OUT:rdisp/max_wprun_time조정 또는 SQL 튜닝TSV_TNEW_PAGE_ALLOC_FAILED: 메모리 부족 → ST02 파라미터
- Source Code Position + Callstack 수집
- 재현 가능성 테스트 (DEV에서 시나리오 재실행)
2. Work Process 행 (SM50/SM66)
- SM50 → Running 상태 프로세스 확인
- Table, Action, Time 컬럼 주목
- 동일 Report/테이블이 여러 프로세스에서 Running → 데드락 또는 SQL 튜닝 필요
- SM66 전 서버 조회 (분산 환경)
- Terminate with Core 결정은 영향 평가 후
- ST05 SQL Trace로 원인 프로세스 심층 분석
3. Transport 실패 (STMS)
- STMS → Import Queue → 실패 요청 확인
- Return Code:
- 0~4: 경고/정보 (무시 가능)
- 6: 경고 (검토 권장)
- 8: 오류 (원인 분석 필수)
- 12: 중단 (심각, 시스템 점검)
- tp 로그:
/usr/sap/trans/log/ALOG<YY>.<SID>: 전체 액션 로그ULOG<YY>.<SID>: 사용자 로그SLOG<YY>.<SID>: Short log
- 한국 현장 빈도 높은 원인:
- 한글 Short Text 변환 실패 (tp Unicode 이슈)
- 의존 오브젝트 누락 (Preceding TR 미import)
- Domain/Data Element 활성화 실패
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 · 184 lines · 94 tokens per session scan A 71a857d45627
sap-basis-consultant is an agent published in the GitHub repository BoxLogoDev/sapstack (20 stars, last pushed 23d ago), licensed MIT. It adds 94 tokens to every session and 2,377 once invoked, about $0.0004 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 agents, from other repositories
sap-code-grep
Mechanical, exhaustive grep/count over a mandatory local ABAP source snapshot — MESSAGE statements, branches, AUTHORITY-CHECK, flow-control exits, and log-cell messages. Rejects requests without a complete, readable local source folder. Returns only structured count tables, never raw source dumps.
abap2ui5-reviewer
Reviews an abap2UI5 app class (a z2ui5ifapp implementation and its .clas.xml) against the abap2UI5 rules - UI5 names that do not exist in the oldest supported release, binding rules, roundtrip and state pitfalls, view-builder chain layout and abapGit sidecar format. Read-only; reports findings with file:line. Use…
abap-debugger
Control ABAP debugging sessions - breakpoints, stepping, variables.
abap-troubleshooter
Analyze runtime dumps and performance traces.
abap-usage-analyzer
Analyze where ABAP objects are used, dependencies, and change impact.
cap-performance-debugger
Use this agent when optimizing CAP application performance, troubleshooting errors, debugging issues, or implementing monitoring. This agent specializes in query optimization, performance tuning, and problem diagnosis. Examples: "Why is my CQL query slow?" "Optimize this SELECT query with associations" "Debug '500…