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 skills add BoxLogoDev/sapstack --skill sap-qmgit 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/skills/boxlogodev/sapstack/sap-qm)<a href="https://agentmods.dev/skills/boxlogodev/sapstack/sap-qm"><img src="https://agentmods.dev/badge/skills/boxlogodev/sapstack/sap-qm/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/skills/boxlogodev/sapstack/sap-qm"><img src="https://agentmods.dev/badge/skills/boxlogodev/sapstack/sap-qm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00163 | $0.12338 |
| Opus 5.5 | $0.00065 | $0.04935 |
| Sonnet 5.5 | $0.00033 | $0.02468 |
| Haiku 4.5 | $0.00016 | $0.01234 |
Grade A, and why
sap-qm 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 — 1,240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Quality Management (QM) Skill
1. Environment Intake Checklist
Before starting QM troubleshooting or configuration, collect:
- SAP Release: ECC 6.0 (SP number), S/4HANA 1909+, S/4HANA Cloud
- Deployment: On-premise (ECC/S/4 OP) | Private Cloud (RISE) | Public Cloud (SAP QMS)
- QM Activation:
SPRO > SAP Customizing for Quality Managementconfigured? - Scope: 구매(MM) 수입검사 | 생산(PP) 공정검사 | 판매(SD) 납품검사
- Industry: 제조업(일반) | 화학 | 제약(GMP) | 식품(HACCP) | 자동차(IATF 16949)
- Quality Strategy: 100% 검사 | Sampling plan (AQL-based) | Zero-inspection (trusted supplier)
- Integration: MM-QM 구매검사 | PP-QM 공정검사 | SD-QM 납품검사 | QM-PM 통지서 연동
Skill will adapt all answers to user's specific SAP release, deployment, and industry context.
2. Quality Planning (QP01/QP02/QP03, QS21/QS31, QDV1)
2.1 Inspection Plan Structure (검사계획)
Transaction: QP01 (Create), QP02 (Change), QP03 (Display)
Logical hierarchy:
Inspection Plan Header (PLKO)
├─ Plan Number (PLNNR): 자동 또는 수동 부여
├─ Material (PLKO-MATNR) + Plant (PLKO-WERKS)
├─ Inspection Type (PLKO-LOART):
│ ├─ 01: Purchasing (구매 입고 검사)
│ ├─ 03: Production (공정 검사)
│ ├─ 04: Sales (판매 출고 검사)
│ └─ 08/09: Recurring/Source
├─ Valid from/to (PLKO-GDATU ~ PLKO-GDATU_END)
└─ Status: 1=Created, 2=Released, 3=Locked
└─ Inspection Operations (PLPO) — 검사 단계별
├─ Operation number (OPNR): 10, 20, 30...
├─ MICs (Master Inspection Characteristics — PLMK)
└─ Sampling Procedure (QDV1 reference)
Key Tables:
PLKO: Plan header (Inspection plan name, type, dates)PLPO: Plan operations (Operation sequencing, MIC assignment)PLMK: Plan-MIC assignment (QPMK reference)QPMK: Master Inspection Characteristics (검사특성 마스터)
한국 현장 팁: IATF 16949 대비 각 Operation마다 검사기준(Specification) 명확히 입력 필수. LSL/Target/USL 3개 다 입력.
2.2 Master Inspection Characteristics (MIC) — QS21/QS31
QS21 Transaction (Create MIC):
- MIC Code (QPMK-MERKM): 산도, 경도, 수분율, Tensile strength 등
- Type (QPMK-MERTY): 1=Quantitative (수치), 2=Qualitative (합격/불합격)
- Unit of measure (QPMK-MEINS): mg/L, HV, %, ppm
- Valuation (QPMK-BWFL): A=Automatic, B=Manual, C=Reference sample
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/best-practices/governance.md 9.5 KB
- references/best-practices/operational.md 5.2 KB
- references/best-practices/period-end.md 8.7 KB
- references/de/quick-guide-de.md 2.2 KB
- references/en/quick-guide-en.md 2.1 KB
- references/img/inspection-plan.md 12 KB
- references/img/inspection-type.md 11 KB
- references/img/overview.md 6.9 KB
- references/img/quality-notification-type.md 12 KB
- references/img/usage-decision.md 13 KB
- references/ja/quick-guide-ja.md 2.0 KB
- references/ko/quick-guide.md 2.3 KB
- references/ko/SKILL-ko.md 335 B
- references/vi/quick-guide-vi.md 2.4 KB
- references/zh/quick-guide-zh.md 1.8 KB
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 · 1,240 lines · 163 tokens per session scan A a9f1516f048a
sap-qm is a skill published in the GitHub repository BoxLogoDev/sapstack (20 stars, last pushed 19d ago), licensed MIT. It adds 163 tokens to every session and 12,338 once invoked, about $0.0007 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-09-04.
Other skills, from other repositories
sap-expert
Expert in SAP ERP systems, ABAP programming, SAP HANA, S/4HANA, Fiori applications, and SAP integration patterns including OData, RFC, and IDoc. Use when the user mentions ERP, enterprise, business apps, ABAP, HANA, or S/4HANA, or when the task involves SAP Ecosystem, ABAP Development, Integration Technologies, or…
sap-customizing
Navigate and understand SAP Customizing (SPRO/IMG). Use when the user asks about customizing settings, SPRO activities, configuration tables, maintenance views, view clusters, or needs to read/understand any customizing data. This skill teaches how to systematically trace from an SPRO activity to the actual tables…
sap-system-personality-report
Generate a comprehensive SAP System Personality Report. Analyzes custom code landscape, functional footprint, development activity, health metrics, and package breakdown. Use when a user asks to characterize a system, understand a system, get a system overview, system report, system personality, or "what does this…
abap-research
Techniques for navigating and finding objects in SAP systems. Use when searching for transactions, programs, FMs, classes, error messages, BAPIs, tables, custom objects, or anything in an unfamiliar SAP system. Teaches the mindset and metadata knowledge a senior ABAP developer uses to find anything in any system. Load…
connect-tool
Use when the user names a specific tool to connect to the agent (an ERP, accounting or desktop program, CRM, WhatsApp, a spreadsheet, a database): research its real docs, choose the safest route, build 01-TOOLS/ / with a test that proves it, and guide the user. NOT a full typed API client (that is…
light-data-engineering
A research data-checking guide for finding, evaluating, preparing, and splitting datasets. It explains whether data can support a study and checks for data leakage, where information accidentally crosses from training data into test data.