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-qm-inspectiongit 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-qm-inspection)<a href="https://agentmods.dev/commands/boxlogodev/sapstack/sap-qm-inspection"><img src="https://agentmods.dev/badge/commands/boxlogodev/sapstack/sap-qm-inspection.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.00051 | $0.00946 |
| Opus 5 | $0.00026 | $0.00473 |
| Sonnet 5 | $0.00010 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
sap-qm-inspection 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.
What it actually says
SAP QM 품질검사 분석
입력: $ARGUMENTS
목표
품질검사 관련 이슈를 체계적으로 분석합니다. 검사로트 상태 확인 → 검사계획 검증 → 결과 기록 안내 → 사용결정 → 후속조치 순서로 진행합니다.
안전 규칙
- 사용결정(Usage Decision)은 사용자 확인 후에만 안내
- 차단 재고 해제는 품질 담당자 승인 필요
실행 절차
Step 1 — 환경 확인
- 검사 유형 (01 수입검사 / 03 공정검사 / 04 출하검사 / 기타)
- 자재번호 또는 검사로트번호
- 플랜트 + SAP 릴리스
- 적용 품질 표준 (ISO 9001 / IATF 16949 / GMP / HACCP)
Step 2 — 검사로트 상태 확인
- QA03 — 검사로트 조회
- 로트 상태: REL (릴리즈) / CALC (결과 기록) / UD (사용결정 완료)
- 검사계획 할당 여부
- 샘플 크기 확인
- QA33 — 검사로트 목록 (미결 로트 일괄 확인)
Step 3 — 검사계획 검증
- QP03 — 검사계획 확인
- MIC (검사특성) 적정성
- 샘플링 절차 (AQL 기준)
- 유효기간 확인
- 검사계획 미할당 시: QM 구성 점검 (자재유형별 검사 설정)
Step 4 — 결과 기록 안내
- QE01/QE51N — 결과 기록
- 정량적 (수치) vs 정성적 (합/부) 구분
- 규격 상한/하한 vs 실측값 비교
- SPC 관리도 참고 (해당 시)
Step 5 — 사용결정 (Usage Decision)
- QA11 — 사용결정 입력
- A (합격) → 재고 자유 사용 전환
- R (불합격) → 차단 재고 유지 → 품질통보 (QM01) 생성
- 조건부 합격 → 부분 입고 처리
- 후속 자동 조치:
- 재고 전기 (합격 시)
- 공급업체 평가 점수 반영 (수입검사 시)
- 품질통보 자동 생성 (불합격 시)
Step 6 — 품질통보 연계 (불합격 시)
- QM01 — 품질통보 생성
- Q1 (고객 클레임) / Q2 (내부) / Q3 (공급업체)
- 결함 코드 + 원인 코드 입력
- 시정조치 작업 할당
- 8D 프로세스 매핑 (해당 시)
업종별 특화
자동차 (IATF 16949)
- PPAP (생산부품승인) 검증
- 공정 능력 지수 (Cp, Cpk) 확인
- 고객 특별 요구사항 반영
제약 (GMP)
- 밸리데이션 상태 확인
- 일탈(Deviation) 처리 절차
- 안정성 시험 이력
식품 (HACCP)
- CCP 모니터링 결과
- 이력추적 (Batch traceability)
위임
- sap-qm-consultant — 상세 QM 분석
- sap-mm-consultant — 입고/차단재고 처리
- sap-pp-consultant — 공정검사 연계
- sap-sd-consultant — 출하검사 + 인증서 발행
참조
plugins/sap-qm/skills/sap-qm/SKILL.mdplugins/sap-qm/skills/sap-qm/references/best-practices/
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 · 87 lines · 0 tokens per session scan A c3a7f6a731f9
sap-qm-inspection is a command published in the GitHub repository BoxLogoDev/sapstack (18 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 946 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
eval-improve
Work the eval-loop corpus — rank failure clusters, fix the top actionable defect, validate against held-out, open a PR.
eval-run
Run an eval case end-to-end on the VM (implement → build → score → record → roll back). VM/full-mode only.
ingest-l1
L1 analysis loop for the abapwiki knowledge base: for each batch it launches the abap-analyzer sub-agent in parallel, then the adversarial judge abap-deepcheck (separate session), applies only the analyses that pass the fail-closed gate, and commits. Resumes exactly after an interruption. Use this skill to document…
research-l2
Executes Phases 1-3 of the L2 process of the abapwiki knowledge base on a slice: launches the abap-functional-researcher sub-agent (gap discovery + multi-source auto-research: wiki -> raw/docs -> MCP abap-fs on the system read-only -> standard knowledge), ingests gaps and evidence, and generates questionnaires for…
ingest-l0
L0 bootstrap of the abapwiki knowledge base: creates stubs for all custom objects from the TADIR. Use this skill to initialize the repo from scratch or to ingest a new TADIR export. Deterministic operations (no LLM sub-agent), idempotent.
btp-architecture-review
Review SAP BTP architecture decisions for account model, services, security, integration, operations, and rollout readiness.