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.
git 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/plugins/sap/open-ux-tools/fiori)<a href="https://agentmods.dev/plugins/sap/open-ux-tools/fiori"><img src="https://agentmods.dev/badge/plugins/sap/open-ux-tools/fiori/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/plugins/sap/open-ux-tools/fiori"><img src="https://agentmods.dev/badge/plugins/sap/open-ux-tools/fiori.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sap-ux-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 yesterday.
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.
What it actually says
{
"name": "sap-ux-fiori-tools",
"version": "1.16.0",
"description": "MCP server and skills for SAP Fiori development. Build, modify, and test SAP Fiori Elements applications with AI assistance.",
"author": {
"name": "SAP SE",
"email": "[email protected]",
"url": "https://www.sap.com"
},
"homepage": "https://github.com/SAP/open-ux-tools/tree/main/plugins-coding-agents/fiori",
"repository": "https://github.com/SAP/open-ux-tools",
"license": "Apache-2.0",
"keywords": [
"sap",
"fiori",
"ui5",
"cap",
"mcp",
"fiori-elements"
]
}
What it installs
The manifest is a name and a version. 6 skills, 1 MCP server travel with it, and installing the plugin installs all of them — 458 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
- yesterday Changed 983deffd21bf
- 2d ago Changed 0f40633d3ca0
- 5d ago Changed 7826356eee64
- 7d ago Changed 6cae955fbaca
- 8d ago First seen · 22 lines scan A 0ea22ce14361
sap-ux-fiori-tools is a plugin published in the GitHub repository SAP/open-ux-tools (158 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-08.
Other plugins, from other repositories
abap2ui5
Build abap2UI5 apps with an agent: the build-an-app, view-chain-layout, abap-check and ui5-check skills, the /abap2ui5:new-app, check, add-ai, find-sample and explain commands, an abap2ui5-reviewer subagent, a hook that runs the abap2UI5 linter on every edited class (where the project has it installed), plus the…
kit
Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.
pict-test-designer
Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for any piece of requirements or code. Analyzes inputs, generates PICT models with parameters, values, and constraints for valid scenarios using pairwise testing. Outputs the PICT model, markdown table of test cases, and expected…
local-test-plugin
Symlink-based local plugin testing for development workflow.
claude-md-management
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.