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-tree-tablegit 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-tree-table)<a href="https://agentmods.dev/skills/sap/open-ux-tools/sap-fiori-tree-table"><img src="https://agentmods.dev/badge/skills/sap/open-ux-tools/sap-fiori-tree-table/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-tree-table"><img src="https://agentmods.dev/badge/skills/sap/open-ux-tools/sap-fiori-tree-table.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00037 | $0.00873 |
| Opus 5 | $0.00018 | $0.00436 |
| Sonnet 5 | $0.00007 | $0.00175 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
sap-fiori-tree-table 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Fiori Tree Table with Recursive Hierarchy
Purpose
Configure hierarchical tree table to display parent-child relationships in a recursive structure (organizational hierarchies, category trees, nested data).
Environment Requirements
CAP Projects:
- ✅ VS Code or SAP Business Application Studio (BAS) - Both environments supported
- ✅ Fiori MCP Server - Required for Fiori app generation and modification (VS Code only)
- ✅ CDS MCP Server - Required for CDS model queries
ABAP RAP Projects:
- ✅ VS Code only - ABAP Development Tools extension is VS Code-specific
- ✅ Fiori MCP Server - Required for Fiori app generation and modification
- ✅ ABAP Development Tools for VS Code extension - Required for backend development (includes ADT MCP server for RAP operations)
MANDATORY: Gather Required Inputs First
STOP and ASK the user for ALL of these inputs if ANY are missing from the prompt:
For ABAP RAP Projects:
- Package name - Where to create or find backend hierarchy objects ($TMP for local, or specific package like Z_MAINT)
- Transport Required: Depends on package type (No for local packages like $TMP, Yes for transportable packages)
- Entity name - The entity to make hierarchical (e.g., "Equipment", "Category", "FunctionalLocation")
For CAP Projects:
- Entity name - The entity to make hierarchical (e.g., "Travel", "Category", "ProductCategory")
DO NOT proceed with implementation until all inputs are confirmed.
CAP Implementation
📖 Complete CAP Implementation Guide
Quick Summary:
- 6-step process: Check entity → Add association → Add @hierarchy → Configure manifest → Create data → Test
- Supports UUID, String, and Integer keys (single key only)
- Requires @sap/cds 9.6.0+ and OData V4
- Use CDS MCP to search model before editing
ABAP RAP Implementation
What ships with it
9 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.
- references/cap/implementation.md 6.3 KB
- references/rap/detailed-guides/0-rap-generator-requirements.md 1.8 KB
- references/rap/detailed-guides/1-read-only-treeviews.md 5.3 KB
- references/rap/detailed-guides/2-editable-treeviews.md 5.4 KB
- references/rap/detailed-guides/2.1-prerequisites-and-concepts.md 6.8 KB
- references/rap/detailed-guides/2.2-treeviews-introduction.md 4.1 KB
- references/rap/detailed-guides/2.3-with-generator.md 14 KB
- references/rap/detailed-guides/2.4-troubleshooting-checklist.md 16 KB
- references/rap/implementation.md 4.8 KB
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 · 95 lines · 37 tokens per session scan A 559be568ba39
sap-fiori-tree-table is a skill published in the GitHub repository SAP/open-ux-tools (158 stars, last pushed yesterday), licensed Apache-2.0. It adds 37 tokens to every session and 873 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-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…
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.