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-korean-tax-invoice-debuggit 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-korean-tax-invoice-debug)<a href="https://agentmods.dev/commands/boxlogodev/sapstack/sap-korean-tax-invoice-debug"><img src="https://agentmods.dev/badge/commands/boxlogodev/sapstack/sap-korean-tax-invoice-debug.svg" alt="Measured on agentmods" 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 | $0.00067 | $0.01690 |
| Opus 5 | $0.00034 | $0.00845 |
| Sonnet 5 | $0.00013 | $0.00338 |
| Haiku 4.5 | $0.00007 | $0.00169 |
Grade A, and why
sap-korean-tax-invoice-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 4d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
전자세금계산서 디버그 파이프라인
입력: $ARGUMENTS
🎯 목표
한국 전자세금계산서 발행·수취·역발행 오류를 체계적으로 진단합니다. 한국 부가가치세법 및 국세청 국세청 홈택스 연계 맥락을 포함합니다.
🔒 안전 규칙
- 실제 사업자등록번호 추정 금지 — 사용자가 제공
- 공인인증서 경로·비밀번호 절대 예시로 제시 금지
- 운영 환경 STRUST 변경은 Transport 경유
Step 1. 증상 분류
질문:
- 오류 단계:
- 발행 (Issuing) — VF01 → Provider 전송
- 수취 (Receiving) — MIRO → 매입 승인번호 연계
- 역발행 (Reversal) — 반품·수정 전자세금계산서
- Provider: SAP DRC / 이카운트 / 비즈플레이 / SmartBill / 더존 / 커스텀
- SAP 릴리스: ECC / S/4HANA
- CVI KR (Country Version Korea) 활성화 여부
Step 2. 발행 (Issuing) 이슈
2-1. VF01 빌링 포스팅 실패
- SE16N → J_1BNFE: Brazil-based Korean e-Tax 구조
- VFBS: 빌링 포스팅 오류 로그
- 승인번호 필드 누락 → 환경 설정 확인
2-2. Provider 전송 실패
- SMICM → HTTP Log: 외부 호출 상태
- SMQ1 / SMQ2: qRFC 큐 점검
- SXMB_MONI (PI/PO 경유 시): 메시지 상태
- CPI Dashboard (BTP 경유 시): iFlow 상태
2-3. 인증서 (STRUST) 문제
- STRUST: SSL Client (Standard) 또는 SSL Client (Anonymous)
- 한국 공인인증서:
- 루트 CA: 한국정보인증 / 코스콤 / NICE평가정보
- 유효기간 확인 (연 1회 갱신)
- TLS 1.2+ 필수 (KISA 가이드)
ssl/ciphersuites파라미터 확인
2-4. 국세청 API 응답 오류
- 승인번호 반환 없음 → 접수 실패
- 사업자등록번호 불일치
- 품목 코드 규격 오류
- 금액 소수점 오류 (KRW는 0)
Step 3. 수취 (Receiving) 이슈
3-1. MIRO 입력 시 승인번호 불일치
- PO 기반 → Info record 세금 설정
- J_1BNFE 구조 필수 필드
- 매입 승인번호 = 매출측 발행번호
- 국세청 홈택스 실시간 조회 (on-demand)
3-2. 부가세 매입 공제 vs 불공제
- FTXP: Tax Code 설정
- 매입세액 공제 대상 여부 (차량·접대비 등 불공제)
- Account Determination (OBYC → VST)
3-3. 송장 차단
- MRBR 조회 → 차단 사유
- Amount/Quantity/Price tolerance
- OMR6: Tolerance 조정
Step 4. 역발행 (Reversal) 이슈
4-1. 수정세금계산서 발행
- 반품 프로세스 (VA01 Return Order + VF01 Credit Memo)
- 원본 승인번호 참조 필수
- 역발행 사유 코드 (1~6)
4-2. 매입자 발행 (한국 특수)
- 매입 기업이 매출 세금계산서를 대신 발행하는 케이스
- 농어민·영세사업자 대상
- 별도 커스텀 구현 필요 (SAP 표준 미지원)
Step 5. 통합 시나리오별 가이드
5-1. SAP DRC (Document and Reporting Compliance)
- S/4HANA 2022+ 네이티브 기능
- 트랜잭션: DRC_EDOC_COCKPIT
- Configuration: Cockpit → Setup for Korea
- 정부 인증 연결 내장
5-2. 3rd-party Provider (이카운트·비즈플레이·SmartBill)
- RFC 또는 REST API 연동
- SM59: RFC Destination 확인
- WE02: IDoc 기반인 경우 IDoc 상태
- Provider dashboard에서 국세청 전송 상태 확인
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.
- 4d ago First seen · 175 lines · 67 tokens per session scan A bc0e32851653
sap-korean-tax-invoice-debug is a command published in the GitHub repository BoxLogoDev/sapstack (18 stars, last pushed 4d ago), licensed MIT. It adds 67 tokens to every session and 1,690 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.
rpt1-fico-predict
Explain local SAP-RPT-1-OSS inference prerequisites for FI/CO CSV experiments and print explicit user-run commands without executing inference.
rpt1-fico-prepare
Inspect a local FI/CO CSV for SAP-RPT-1-OSS preparation risks and print dry-run guidance without modifying files or running inference.