Open UX Tools is a collection of open-source modules for building SAP Fiori applications more efficiently. SAP Fiori developers and related projects use the reusable modules to create development tools and to contribute fixes, findings, and improvements through community collaboration.
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 SAP/open-ux-tools --skill sap-fiori-app-developmentgit clone --depth 1 https://github.com/SAP/open-ux-toolsWrote 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/sap/open-ux-tools/sap-fiori-app-development)<a href="https://agentmods.dev/skills/sap/open-ux-tools/sap-fiori-app-development"><img src="https://agentmods.dev/badge/skills/sap/open-ux-tools/sap-fiori-app-development/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/sap/open-ux-tools/sap-fiori-app-development"><img src="https://agentmods.dev/badge/skills/sap/open-ux-tools/sap-fiori-app-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00033 | $0.01467 |
| Opus 5 | $0.00016 | $0.00733 |
| Sonnet 5 | $0.00007 | $0.00293 |
| Haiku 4.5 | $0.00003 | $0.00147 |
Grade A, and why
sap-fiori-app-development 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Fiori App Development Guidelines (CAP & Standalone Projects)
General Guidelines (Applicable to CAP and Standalone Fiori Projects)
- Always ask the user whether they want to create a Fiori app for CAP (Cloud Application Programming) or a standalone Fiori project connected to an external OData service before proceeding with implementation, unless the technology stack is explicitly specified in the user's request.
- Use the Fiori MCP tools to create the Fiori UI using SAP Fiori Elements.
- After the Fiori MCP Server tools execute successfully, inform the user of completion. Do not verify or double-check - treat successful tool execution as confirmation.
- The data model should be suitable for SAP Fiori elements: at minimum one entity type that serves as the main entity for the application. Navigation properties to related entities are optional but enable richer UI patterns.
- Each property of an entity must have a proper datatype.
- Before modifying the code directly - first check whether Fiori MCP server provides a suitable function or tool, or if a specialized skill exists (e.g.
sap-fiori-analytical-chart).
Available Application Templates (Both CAP and Standalone Projects)
The Fiori MCP can create the following application templates for both CAP and standalone project backends:
- FE_LROP - List Report Object Page (most common, OData V2/V4)
- FE_ALP - Analytical List Page (OData V2/V4)
- FE_OVP - Overview Page (OData V2/V4)
- FE_WORKLIST - Worklist (OData V2/V4)
- FE_FEOP - Form Entry Object Page (OData V4 only)
- FE_FPM - Flexible Programming Model / Custom Page (OData V4 only)
- FF_SIMPLE - Basic SAPUI5 Freestyle template (can work without a data source)
Available Page Types
The Fiori MCP can add the following page types to existing applications:
- ListReport - Table view with filtering and search
- ObjectPage - Detail page for viewing/editing records
- CustomPage - Fully custom page with your own views
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 Changed · +3 lines 1a0667a0b13b
- 12d ago First seen · 91 lines · 33 tokens per session scan A 453eb56d4c3b
sap-fiori-app-development is a skill published in the GitHub repository SAP/open-ux-tools (158 stars, last pushed today), licensed Apache-2.0. It adds 33 tokens to every session and 1,467 once invoked, about $0.0002 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 skills, from other repositories
fix-xml-globals
Fix XML view/fragment issues that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs these rules: no-globals - For ALL global variable access in XML views — sap., jQuery., AND app-namespace globals (e.g., com.example.app.utils.Handler.onPress, my.app.formatter.method) no-ambiguous-event-handler…
fix-linter-blind-spots
Fix runtime-breaking patterns in JS files that the UI5 linter does NOT report. Use this skill when: Tests fail after modernization with "ReferenceError", "TypeError: Cannot read properties of undefined", or "X is not defined" The linter shows zero remaining errors but tests still crash at runtime Phase 3, Step 3.2 of…
modernize-flp-sandbox
Use when migrating UI5 apps from legacy FLP sandbox to the new sandbox (New Sandbox). Triggers on /modernize-flp-sandbox, mentions of "flpSandbox.html", "sap-ushell-config", or requests to update sandbox configuration.
fix-control-renderer
Fix Control renderer issues that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs these rules: no-deprecated-control-renderer-declaration - For missing renderer declaration, string-based renderer declaration, implicit renderer auto-discovery (removed in modern UI5) no-deprecated-api - For…
fix-deprecated-controls
Fix deprecated control/class/interface/type issues that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs: no-deprecated-api with messages about deprecated class, interface, type, property, or property of class Messages like "Use of deprecated class '...'", "Use of deprecated interface '...'"…
fix-fiori-elements-extensions
Handle Fiori Elements V2 controller extensions during UI5 modernization. Use this skill when: Extension controllers use sap.ui.controller() AND the manifest has a matching controllerName entry (Case B → report only, do not modernize) Extension controllers use Controller.extend() with manifest controllerName…