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.
Borrowing it
Nothing to install: this file belongs to SAP/open-ux-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SAP/open-ux-tools/main/.agents/skills/create-skill-sap-fiori-tools/SKILL.mdgit 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/create-skill-sap-fiori-tools)<a href="https://agentmods.dev/skills/sap/open-ux-tools/create-skill-sap-fiori-tools"><img src="https://agentmods.dev/badge/skills/sap/open-ux-tools/create-skill-sap-fiori-tools/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/create-skill-sap-fiori-tools"><img src="https://agentmods.dev/badge/skills/sap/open-ux-tools/create-skill-sap-fiori-tools.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.00151 | $0.04165 |
| Opus 5.5 | $0.00060 | $0.01666 |
| Sonnet 5.5 | $0.00030 | $0.00833 |
| Haiku 4.5 | $0.00015 | $0.00417 |
Grade A, and why
create-skill-sap-fiori-tools 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 9d 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Skill — SAP Fiori Tools
Author skills for the open-ux-tools ecosystem, regardless of where they live on disk. This skill enforces the conventions that make SAP Fiori Tools skills portable across SAP-approved AI coding assistants (Github Copilot, Claude) and development environments (VS Code, SAP Business Application Studio) — and safe to ship publicly.
Skill location is an input, not a convention. Different hosts and repos use different directories (
.agents/skills/for contributor skills,~/.agents/skills/for user skills,packages/fiori-mcp-server/skills/for public skills in this monorepo, etc.). Ask the user where the skill should be created (or refactored) and treat that path as the target directory throughout. This SKILL.md never assumes a specific location.
Why a dedicated creator? Generic skill-creator advice is not enough here. Our skills must run in multiple hosts, target two backends (CAP + ABAP RAP), two OData versions (V2 + V4), and two audiences (internal developers vs. public end users). This skill captures those constraints so authors do not have to rediscover them.
Step 0 — Classify the skill (do this first)
Before writing anything, decide who the skill is for. This drives every later choice.
| Category | Audience | Examples in this repo | Ships publicly? |
|---|---|---|---|
| Public | Developers building SAP Fiori apps (CAP or standalone) | sap-fiori-app-development, sap-fiori-analytical-chart, sap-fiori-tree-table, sap-fiori-create-cli, sap-fiori-eslint-plugin, sap-fiori-opa5-test-development, sap-fiori-add-visual-filter |
Yes |
| Contributor | Engineers working on the open-ux-tools monorepo itself |
eslint-rule-development, odata-vocabularies-sync |
No — monorepo-only |
Naming convention (mandatory)
| Category | Pattern | Example |
|---|---|---|
| Public | sap-fiori-<feature> (kebab-case, feature-scoped, no product-suffix like -cli unless the skill is the CLI) |
sap-fiori-tree-table, sap-fiori-analytical-chart |
| Contributor | <domain>-<action> (kebab-case; no sap-fiori- prefix so it is obvious the skill is not public) |
eslint-rule-development, odata-vocabularies-sync |
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.
- 9d ago First seen · 281 lines · 151 tokens per session scan A 9111b1776435
create-skill-sap-fiori-tools is a skill published in the GitHub repository SAP/open-ux-tools (159 stars, last pushed today), licensed Apache-2.0. It adds 151 tokens to every session and 4,165 once invoked, about $0.0006 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-10-15.
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-cyclic-deps
Detect and resolve cyclic module dependencies introduced during UI5 modernization. Trigger when user mentions: "cyclic dependency", "circular import", "undefined module at runtime", "lazy require", "sap.ui.require sync", "import cycle", or when a module returns undefined despite a correct import path. Classic symptom…
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…
fix-js-globals
Fix JavaScript no-globals errors that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs: no-globals rule with message "Access of global variable '...' (...)" in JS files Cases handled (linter CANNOT auto-fix): Assignments to global namespaces: sap.myNamespace = {...} Global namespace…
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.