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 efeumutaslan/SAP-SKILLS --skill sap-successfactorsgit clone --depth 1 https://github.com/efeumutaslan/SAP-SKILLSWrote 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/efeumutaslan/sap-skills/sap-successfactors)<a href="https://agentmods.dev/skills/efeumutaslan/sap-skills/sap-successfactors"><img src="https://agentmods.dev/badge/skills/efeumutaslan/sap-skills/sap-successfactors/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/efeumutaslan/sap-skills/sap-successfactors"><img src="https://agentmods.dev/badge/skills/efeumutaslan/sap-skills/sap-successfactors.svg" alt="Reviewed on agentmods" width="80" 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.00081 | $0.02790 |
| Opus 5 | $0.00041 | $0.01395 |
| Sonnet 5 | $0.00016 | $0.00558 |
| Haiku 4.5 | $0.00008 | $0.00279 |
Grade A, and why
sap-successfactors scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const tokenResponse = await axios.post( How it starts
The opening of the file, as written. The whole thing — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP SuccessFactors HXM Development
Related Skills
sap-security-authorization— XSUAA/IAS for BTP-side extensionssap-s4hana-extensibility— Hybrid HR/Finance integration scenariossap-integration-suite-advanced— Pre-built SF iFlows and API Managementsap-event-mesh— SF Intelligent Services events to BTP Event Meshsap-cap-advanced— CAP-based BTP extensions consuming SF APIs
Quick Start
Choose your development approach:
| Scenario | Approach | API |
|---|---|---|
| Read/write employee data | OData V2 API | /odata/v2/ endpoints |
| Custom business objects | MDF (Metadata Framework) | MDF OData API |
| Event-driven extension | Intelligent Services | Event triggers → BTP |
| Analytics / reporting | People Analytics OData | $metadata reporting |
| UI extension | Extension Center | Custom UI on SF pages |
| Integration | SAP Integration Suite | Pre-built iFlows |
Minimal API call — Get employee by ID:
GET https://<api-server>/odata/v2/User('EMPL001')
?$select=userId,firstName,lastName,email,department
&$format=json
Authorization: Bearer <oauth_token>
Core Concepts
API Architecture
- OData V2: Primary API protocol for all SuccessFactors entities
- Entity sets: Map to business objects (User, EmpJob, EmpEmployment, PerPersonal, etc.)
- Compound Employee API: Single request for employee + all related entities
- Associations: Navigate between entities (
User('ID')/directReports) - Effective dating: Most HR entities have
startDate/endDatefor temporal data
Metadata Framework (MDF)
- Generic Objects (GOs): Custom business objects defined via MDF
- Rules engine: Business rules attached to MDF objects (onInit, onSave, onChange)
- Picklists: Reusable value lists for dropdowns
- Association types: 1:1, 1:N, configurable navigation
- MDF OData: Auto-generated OData endpoints for custom MDF objects
Permission Model (RBP)
- Role-Based Permissions (RBP): Foundation of SF security
- Permission roles: Group of permission grants assigned to users
- Target population: Which employees a role can access (granting rules)
- Permission groups: Logical grouping of entities and fields
- Field-level permissions: Control read/write/hidden per field per role
What ships with it
1 file 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.
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.
- 12d ago First seen · 305 lines · 81 tokens per session scan A 9dce092c41fa
sap-successfactors is a skill published in the GitHub repository efeumutaslan/SAP-SKILLS (5 stars, last pushed 5mo ago), licensed MIT. It adds 81 tokens to every session and 2,790 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
cao-provider
Create a new CLI agent provider for CAO (CLI Agent Orchestrator). Use this skill whenever the user wants to add support for a new CLI-based AI agent (e.g., a new coding assistant CLI), integrate a new provider, or scaffold a provider implementation. Also use when the user asks about the provider architecture, what…
adt-api-discovery
Investigate SAP ADT REST API endpoints. Use when the user asks about ADT API endpoints, request/response XML formats, content types, or how a specific ADT feature works under the hood. Teaches how to trace from discovery documents → RESAPP classes → handler classes → Simple Transformations → XML schemas. Requires the…
api-design
REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.
ask-opencli
A helper for asking Grok or Gemini through OpenCLI, which uses an already signed-in Chrome browser session instead of a paid API.
gemma4-local-deploy
A guide for running Gemma 4 12B, an AI language model, locally on a Mac or Apple Silicon computer. It uses downloaded model files and a local service that provides an OpenAI-compatible API or Ollama access when requested.
config-secrets-environments
Design, audit, and verify configuration, environment separation, secrets, BYOK flows, key rotation, config schema validation, and drift checks across local, dev, staging, and production. Use when adding env vars, changing runtime config, handling API keys or user-provided keys, diagnosing config drift, or preparing…