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-opa5-test-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-opa5-test-development)<a href="https://agentmods.dev/skills/sap/open-ux-tools/sap-fiori-opa5-test-development"><img src="https://agentmods.dev/badge/skills/sap/open-ux-tools/sap-fiori-opa5-test-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-opa5-test-development"><img src="https://agentmods.dev/badge/skills/sap/open-ux-tools/sap-fiori-opa5-test-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk fail
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 243 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00145 | $0.03536 |
| Opus 5 | $0.00072 | $0.01768 |
| Sonnet 5 | $0.00029 | $0.00707 |
| Haiku 4.5 | $0.00015 | $0.00354 |
Grade A, and why
sap-fiori-opa5-test-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 11d 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Fiori OPA5 Development Skill
A guide for writing, fixing, and extending OPA5 integration tests for SAP Fiori Elements applications.
Covers both OData V4 (sap.fe.test) and OData V2 (fioriElementsTestLibrary).
Not applicable to freestyle UI5 applications - for those, suggest the ui5-best-practices-opa5 skill from the UI5 Plugins for Coding Agents ui5.
Prerequisites
This skill requires an existing SAP Fiori Elements application generated by SAP Fiori tools with a test folder present (e.g. at webapp/test). If it is missing, follow the version-specific guide after detecting the OData version.
Step 1: Locate the Project Root
When the user provides a project name or ID (e.g. fin.test.rap.lr3) instead of a file path:
- Search for
manifest.jsonfiles under common project roots (e.g.webapp/manifest.json). - Match the
"id"field insap.appto the given name, or look for a folder whose name contains the given ID. - Once found, treat the folder containing
webapp/manifest.jsonas the project root for all subsequent steps.
Step 2: Detect OData Version
Before writing any test code, determine whether the app is OData V4 or V2. The two test libraries are completely different and must never be mixed.
Primary check: manifest.json
| What you find | Version | Test library |
|---|---|---|
"sap.fe.templates" key inside sap.ui5.dependencies.libs |
V4 | sap.fe.test |
"sap.ui.generic.app" as a root key |
V2 | fioriElementsTestLibrary |
Fallback check: metadata.xml
If manifest.json is inconclusive, check the <edmx:Edmx> root element in the service metadata file (typically at webapp/localService/mainService/metadata.xml, or wherever metadataPath points in ui5-mock.yaml):
| Attribute value | Version |
|---|---|
xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx" or Version="4.0" |
V4 |
xmlns:edmx="http://schemas.microsoft.com/ado/2007/06/edmx" or Version="1.0" |
V2 |
What ships with it
7 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.
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.
- 11d ago First seen · 294 lines · 145 tokens per session scan A 717810bba70a
sap-fiori-opa5-test-development is a skill published in the GitHub repository SAP/open-ux-tools (158 stars, last pushed yesterday), licensed Apache-2.0. It adds 145 tokens to every session and 3,536 once invoked, about $0.0007 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
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
playwright-component-testing
Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.
next-partial-prefetching-optimizer
Optimize what selected Next.js client navigations include before the click under Partial Prefetching. Use after Cache Components and Partial Prefetching are adopted when the user wants selected URL-specific UI to be instant, wants reusable content to wait for navigation, or needs to choose between default, viewport…
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
vscode-visual-regression
Write Storybook stories and visual regression tests for the Kilo VS Code extension webview UI.
verify
Build, launch, drive, and screenshot the OpenNOW Electron settings UI on Windows.