fix-fiori-elements-extensions

fix-fiori-elements-extensions is a skill for Claude Code, Codex from UI5/plugins-coding-agents. It costs 204 tokens per session (3,871 once invoked), scanned A, original, Apache-2.0.

A modernization guide for controller extensions in SAP Fiori Elements V2, a framework for generating business-app user interfaces.

In plain words
What is it for?
Use it to handle deprecated controller-extension APIs, including migration to the newer ControllerExtension pattern when the project uses the supported registration method.
Why use it?
It distinguishes extensions that should be changed from those that should only be reported, avoiding unsafe edits to manifest-registered controllers.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/ui5/plugins-coding-agents/fix-fiori-elements-extensions
Any agent
npx skills add UI5/plugins-coding-agents --skill fix-fiori-elements-extensions
Clone the repo
git clone --depth 1 https://github.com/UI5/plugins-coding-agents

Made for: Claude Code, Codex.

Per session 204 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,871 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00204 $0.03871
Opus 5 $0.00102 $0.01936
Sonnet 5 $0.00041 $0.00774
Haiku 4.5 $0.00020 $0.00387

Measured 3d ago against content hash 9d3d6ad9d900, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fix-fiori-elements-extensions 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 3d 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.

plugins/ui5-modernization/skills/fix-fiori-elements-extensions/SKILL.md · 407 lines

How it starts

The opening of the file, as written. The whole thing — 407 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fix Fiori Elements Controller Extensions

This skill handles Fiori Elements V2 controller extensions during UI5 modernization. There are two cases with different actions:

  • Case B (most common): Extensions registered via controllerName in manifest → Report only. Do NOT modify the controller files. Leave them as-is and inform the user which files need manual attention.
  • Case A (rare): Extensions using registerControllerExtensions → Perform the full modernization to ControllerExtension.extend() + manifest registration.

Linter Rules Handled

Rule ID Message Pattern This Skill's Action
no-deprecated-api Use of deprecated registerControllerExtensions Case A: Modernize to manifest + ControllerExtension
no-deprecated-api Use of deprecated sap.ui.controller Case B (if manifest has controllerName): report only, do not fix; Case A (if registerControllerExtensions): ControllerExtension class
no-deprecated-api Use of deprecated Controller (from sap/ui/core/mvc/Controller) Case B: report only, do not fix

Quick Decision: Which Case Am I?

Is there a `controllerName` entry in manifest.json under
sap.ui5/extends/extensions/sap.ui.controllerExtensions with a SIMPLE key
(no "#" in the key)?
  ├── YES → Case B: DO NOT MODERNIZE. Report the file(s) and move on.
  │         (regardless of whether source uses sap.ui.controller() or Controller.extend())
  └── NO  → Is there a registerControllerExtensions call in JS?
              ├── YES → Case A: modernize to ControllerExtension.extend() + manifest with #stableId key
              └── NO  → This skill does not apply

When to Use

Case B (most common) — Detected when the manifest already has a controllerName entry under a simple key, and the controller file uses either sap.ui.controller() or Controller.extend():

// manifest.json — controllerName registration already present (simple key, no "#")
"sap.ui.controllerExtensions": {
    "sap.suite.ui.generic.template.ListReport.view.ListReport": {
        "controllerName": "my.app.ext.controller.ListReportExt"
    }
}

Read the full file on GitHub · 407 lines

Changes

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.

  1. 3d ago First seen · 407 lines · 204 tokens per session scan A 9d3d6ad9d900

Subscribe to this mod's changes

fix-fiori-elements-extensions is a skill published in the GitHub repository UI5/plugins-coding-agents (34 stars, last pushed yesterday), licensed Apache-2.0. It adds 204 tokens to every session and 3,871 once invoked, about $0.0010 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.

Related

Other skills, from other repositories

plugin-init

初始化 Zhin.js 插件项目。Use when asked to create a new plugin, scaffold plugin structure, or set up a plugin project. 引导生成符合 Plugin Runtime 规范的目录结构、package.json、plugin.ts、约定能力目录和 README。.

zhinjs/zhin · 56 tokens

plugin-publish

发布 Zhin.js 插件到 npm 和 Zhin 插件市场。Use when asked to publish a plugin, prepare for release, check publish readiness, or submit to the Zhin plugin marketplace. 引导完成发布前检查、版本管理和提交流程。.

zhinjs/zhin · 58 tokens

plugin-develop

Implement Zhin.js plugin features with Plugin Runtime: defineCommand, defineAgentTool, middleware, pages. Use when asked to add a command, register a tool, wire cron, extend middleware, or build a console page. Triggers: 插件开发, add command, 加命令, 写插件功能, defineCommand.

zhinjs/zhin · 70 tokens

wordpress-plugin-fundamentals

Modern WordPress plugin development with PHP 8.3+, OOP architecture, hooks system, database interactions, and Settings API.

bobmatnyc/claude-mpm-skills · 32 tokens

view-chain-layout

The layout rules for a z2ui5clui5viewbuilder chain - one call per line, four spaces per tree level, the end( ) column, which factory( ) shape goes with which chain shape, blank lines, and the linter rule that checks them. Identical in abap2UI5, abap2UI5/samples, abap2UI5/samples-controls and abap2UI5/samples-stack.…

abap2UI5/samples · 125 tokens

agent-development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development…

mahmoud20138/Tradecraft · 80 tokens