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-pmgit 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-pm)<a href="https://agentmods.dev/skills/boxlogodev/sapstack/sap-pm"><img src="https://agentmods.dev/badge/skills/boxlogodev/sapstack/sap-pm.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.1 | $0.00211 | $0.09828 |
| Opus 5 | $0.00105 | $0.04914 |
| Sonnet 5 | $0.00042 | $0.01966 |
| Haiku 4.5 | $0.00021 | $0.00983 |
Grade A, and why
sap-pm 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 3d 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 — 830 lines — stays where its author put it; the contents beside it link to each section on GitHub.
1. Environment Intake Checklist
Before answering PM questions, collect:
- SAP Release: ECC 6.0 (which EhP?) or S/4HANA (which release year?)
- Deployment model: On-premise / RISE / Cloud Public Edition
- PM Organization: Planning Plant, Maintenance Plant, Maintenance Coordination Plant
- Industry sector: Manufacturing (automotive, chemicals, electronics), energy, pharma, food & beverage
- Equipment strategy: Single-level (equipment only) vs. two-level (equipment + functional locations)
- Maintenance type focus: Breakdown, preventive, predictive, contract, or combination?
- Integration requirements: MES, predictive maintenance (PAI), mobile (SAP Asset Manager), analytics
2. Equipment Master Data (IE01/IE02/IE03)
Equipment Creation (IE01)
Key T-codes & Menu Path
- IE01: Create Equipment (SPRO → Plant Maintenance → Master Data → Equipment → Create)
- IE02: Change Equipment
- IE03: Display Equipment
- IE10: Create Fleet (for mass equipment with identical configuration)
Critical Fields (EQUI Table)
| Field | Meaning | Mandatory | Notes |
|---|---|---|---|
| EQUNR | Equipment number | Y | Unique 18-char ID; can be internal/external assigned |
| EQKTX | Equipment description | Y | 40 chars; recommend English + Korean |
| EQART | Equipment category | Y | PUMPE (pump), MOTOR (motor), KOMPR (compressor) etc. |
| MATNR | Material master | N | Links to inventory; if serial-tracked material, serializes equipment |
| SERGE | Serial number | N | Hardware serial from nameplate; used in warranty tracking |
| HEQUI | Higher-level equipment | N | Parent equipment (e.g. pump is part of production line) |
| ILOAN | Functional location | Y | Must exist in IFLO before assignment |
| MANDT | Company code | Y | Set at creation; cannot change |
| WERKS | Plant | Y | Maintenance-executing plant |
| KMFID | Manufacturer | N | Free-text; recommend SAP vendor master LIFNR |
| GEWICHT | Weight | N | For spare parts estimation |
| INBDT | Startup date | N | Important for MTBF calculation period |
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.1 KB
- references/best-practices/operational.md 5.9 KB
- references/best-practices/period-end.md 7.0 KB
- references/de/quick-guide-de.md 2.1 KB
- references/en/quick-guide-en.md 2.0 KB
- references/img/equipment-funclocn.md 9.8 KB
- references/img/maintenance-order-type.md 13 KB
- references/img/notification-catalog.md 17 KB
- references/img/overview.md 6.0 KB
- references/img/preventive-maintenance.md 16 KB
- references/ja/quick-guide-ja.md 2.0 KB
- references/ko/quick-guide.md 2.4 KB
- references/ko/SKILL-ko.md 334 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.
- 3d ago First seen · 830 lines · 211 tokens per session scan A 79dfd856b914
sap-pm is a skill published in the GitHub repository BoxLogoDev/sapstack (18 stars, last pushed 7d ago), licensed MIT. It adds 211 tokens to every session and 9,828 once invoked, about $0.0011 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-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-sac-planning
SAP Analytics Cloud (SAC) planning guidance for planning models, planning-enabled stories, data actions, multi actions, version management, data locking, calendar/input workflows, allocations, value driver trees, BPC live planning, and Seamless Planning with SAP Datasphere. Use this for planning design, planning APIs…
sap-sac-custom-widget
SAP Analytics Cloud (SAC) Custom Widget development. Use when building custom visualizations, extending SAC with Web Components, or creating Widget Add-Ons. Covers JSON metadata, JavaScript Web Components, lifecycle functions, data binding with feeds, styling/builder panels, property/event/method definitions…
dependency-upgrade
Secure dependency upgrades with supply chain protection, cooldowns, and staged rollout. Use when upgrading deps, configuring security policies, or preventing supply chain attacks.
sap-dependency-security
SAP dependency security and MCP executable trust policy with secure upgrades, cooldowns, staged rollout, and supply-chain protection. Use when upgrading deps, configuring security policies, preventing supply chain attacks, pinning SAP MCP servers, or reviewing SAP CAP/UI5/Fiori/HANA/Datasphere/SAC/BTP/ABAP dependency…
sap-abap-cds
Comprehensive SAP ABAP CDS (Core Data Services) reference for data modeling, view development, and semantic enrichment. Use when creating CDS views or view entities, defining data models with annotations, working with associations and cardinality, implementing input parameters, using built-in functions, writing CASE…