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-add-visual-filtergit 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-add-visual-filter)<a href="https://agentmods.dev/skills/sap/open-ux-tools/sap-fiori-add-visual-filter"><img src="https://agentmods.dev/badge/skills/sap/open-ux-tools/sap-fiori-add-visual-filter/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-add-visual-filter"><img src="https://agentmods.dev/badge/skills/sap/open-ux-tools/sap-fiori-add-visual-filter.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.00055 | $0.03773 |
| Opus 5.5 | $0.00022 | $0.01509 |
| Sonnet 5.5 | $0.00011 | $0.00755 |
| Haiku 4.5 | $0.00006 | $0.00377 |
Grade A, and why
sap-fiori-add-visual-filter 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 15d 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 — 426 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Fiori Visual Filter
Purpose
Add chart-based filters (Bar/Line) to filter bar or value help dialog (OData V4).
Prerequisites
CAP Projects:
- ✅ VS Code or SAP Business Application Studio (BAS) - Both environments supported
- ✅ Fiori MCP Server - Required for Fiori app modification (VS Code only)
ABAP RAP Projects:
- ✅ VS Code only - ABAP Development Tools extension is VS Code-specific
- ✅ Fiori MCP Server - Required for Fiori app 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:
- Entity - Which entity to add the visual filter to
- Dimension field - The field to filter by (e.g., Category, Status, Destination)
- Measure field - The numeric field to aggregate (e.g., Amount, TotalPrice, ReservationPrice)
- Aggregation method - How to aggregate (see valid values below)
- Chart type - Bar or Line (recommend Bar as default)
DO NOT proceed with implementation until all inputs are confirmed.
⚠️ Line chart dimension type restriction: ChartType: #Line only supports dimensions typed as Edm.Date, Edm.TimeOfDay, or Edm.DateTimeOffset. If the requested dimension is a different type (e.g. string/association code like Status, Category), either use #Bar instead or confirm with the user that the dimension field is a date/time type before proceeding.
CAP Implementation
Enable Aggregation (MANDATORY)
@Aggregation.ApplySupported: {
Transformations: ['aggregate','groupby'],
AggregatableProperties: [{ Property: Amount }],
GroupableProperties: [Category]
}
Aggregated Property (Measure)
Analytics.AggregatedProperty #Amount_sum : {
$Type: 'Analytics.AggregatedPropertyType',
Name: 'Amount_sum',
AggregatableProperty: Amount,
AggregationMethod: 'sum',
![@Common.Label]: 'Total Amount'
}
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.
- 15d ago Changed · +56 lines 713d5c30147c
- 21d ago Changed · +24 tokens per session 6b33b9f65b98
- 23d ago Changed · +119 lines 3cff1a126819
- 1mo ago First seen · 251 lines · 31 tokens per session scan A 210f83596515
sap-fiori-add-visual-filter is a skill published in the GitHub repository SAP/open-ux-tools (160 stars, last pushed today), licensed Apache-2.0. It adds 55 tokens to every session and 3,773 once invoked, about $0.0002 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-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-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-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.
modernize-test-starter
Modernize QUnit unit tests and OPA5 integration tests to the UI5 Test Starter concept. Use this skill when: The linter reports prefer-test-starter for .qunit.html or .qunit.js files Test HTML files use manual sap-ui-core.js bootstrapping instead of Test Starter's runTest.js/createSuite.js Test JS files use…