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-sfsfgit 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-sfsf)<a href="https://agentmods.dev/skills/boxlogodev/sapstack/sap-sfsf"><img src="https://agentmods.dev/badge/skills/boxlogodev/sapstack/sap-sfsf/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-sfsf"><img src="https://agentmods.dev/badge/skills/boxlogodev/sapstack/sap-sfsf.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.00157 | $0.02310 |
| Opus 5 | $0.00078 | $0.01155 |
| Sonnet 5 | $0.00031 | $0.00462 |
| Haiku 4.5 | $0.00016 | $0.00231 |
Grade A, and why
sap-sfsf 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 5d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
1. Environment Detection
□ Which SF modules are active? (EC / ECP / Recruiting / LMS / Performance / Compensation / etc.)
□ Is on-premise HCM still running? (hybrid or full cloud?)
□ Integration middleware? (SAP Integration Suite / BTP / Dell Boomi / MuleSoft / other)
□ SF datacenter region? (affects API base URLs, data residency, release timing)
□ Release version? (SF releases twice per year: 1H = March/April, 2H = September/October)
2. SAP SuccessFactors Module Map
Core HR & Payroll
├── Employee Central (EC) ← System of record — replaces PA/OM
│ ├── Position Management ← Replaces OM positions
│ ├── Time Off ← Replaces IT2001/2002 (partial)
│ └── Time Tracking ← Replaces PT60 (partial)
└── Employee Central Payroll (ECP) ← SAP payroll engine, SF UI
Talent Management
├── Recruiting Management (RCM) ← Job req → offer → hire
├── Onboarding 2.0 ← New hire experience
├── Learning (LMS) ← Training, compliance, certifications
├── Performance & Goals (PMGM) ← Goal setting, reviews, ratings
├── Succession & Development ← Talent pool, career development
└── Compensation ← Merit, bonus, equity planning
Analytics & Planning
├── People Analytics ← Stories (reports), tiles, dashboards
└── Workforce Planning ← Headcount scenarios, workforce modeling
3. Employee Central (EC) Core Concepts
Data model (fundamentally different from HCM infotypes):
- Person → Employment → Job Information (portlets, not infotypes)
- All data is date-effective — changes create new effective-dated records
- No "time constraint" concept — any portlet can have any number of records
Key framework components:
- MDF (Metadata Framework): generic object type → create custom business objects
- Business Rules: condition-based automation → triggered by data changes
- Workflows: approval chains for master data changes → multi-step, conditional routing
What ships with it
11 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 2.2 KB
- references/best-practices/operational.md 1.4 KB
- references/best-practices/period-end.md 1.5 KB
- references/de/quick-guide-de.md 1.8 KB
- references/en/quick-guide-en.md 1.7 KB
- references/ja/quick-guide-ja.md 1.9 KB
- references/ko/quick-guide.md 1.7 KB
- references/ko/SKILL-ko.md 5.8 KB
- references/migration-path.md 7.1 KB
- references/vi/quick-guide-vi.md 1.8 KB
- references/zh/quick-guide-zh.md 1.6 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.
- 5d ago First seen · 250 lines · 157 tokens per session scan A f564273d773f
sap-sfsf is a skill published in the GitHub repository BoxLogoDev/sapstack (18 stars, last pushed 9d ago), licensed MIT. It adds 157 tokens to every session and 2,310 once invoked, about $0.0008 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
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…
product-manager-toolkit
Use when the user needs product management workflows such as RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, go-to-market strategy, feature prioritization, research synthesis, or requirements documentation.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…
ln-51-opportunity-evaluator
Evaluates new product opportunities using demand, channels, competition, and economics. Not for committed-backlog or implementation planning.