open-ux-tools: Skill for Claude Code

.agents/skills/eslint-rule-development/SKILL.md

eslint-rule-development is a skill for Claude Code, Codex from SAP/open-ux-tools. It costs 94 tokens per session (3,020 once invoked), scanned A, original, Apache-2.0.

A development guide for adding rules to an ESLint plugin for SAP Fiori projects. ESLint is a tool that checks source code for agreed rules and problems.

In plain words
What is it for?
Use it to create and test checks for manifests, XML, CDS, flex-change files, or JavaScript and TypeScript code in the Fiori tools plugin.
Why use it?
It provides the project-specific process for validating Fiori files and keeping new rules consistent with the existing codebase.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; installed under .agents/ (shared by several agents).

This is SAP/open-ux-tools's own configuration. It tells Claude Code and Codex how to work on open-ux-tools itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything open-ux-tools configures →

About the project

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.

SAP/open-ux-tools · 159 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to SAP/open-ux-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/SAP/open-ux-tools/main/.agents/skills/eslint-rule-development/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/SAP/open-ux-tools

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for eslint-rule-development

README.md
[![agentmods](https://agentmods.dev/badge/skills/sap/open-ux-tools/eslint-rule-development/github.svg)](https://agentmods.dev/skills/sap/open-ux-tools/eslint-rule-development)
Your own site
<a href="https://agentmods.dev/skills/sap/open-ux-tools/eslint-rule-development"><img src="https://agentmods.dev/badge/skills/sap/open-ux-tools/eslint-rule-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.

agentmods 80×15 button for eslint-rule-development

Your own site · 80×15
<a href="https://agentmods.dev/skills/sap/open-ux-tools/eslint-rule-development"><img src="https://agentmods.dev/badge/skills/sap/open-ux-tools/eslint-rule-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 94 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,020 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
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 20
    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]
How audits are shown
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.1 $0.00094 $0.03020
Opus 5.5 $0.00038 $0.01208
Sonnet 5.5 $0.00019 $0.00604
Haiku 4.5 $0.00009 $0.00302

Measured 14d ago against content hash 48fcc6a423c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

eslint-rule-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 14d 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.

.agents/skills/eslint-rule-development/SKILL.md · 228 lines

How it starts

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

Fiori ESLint Rule Developer

Add a new ESLint rule to @sap-ux/eslint-plugin-fiori-tools following the established patterns in the monorepo.

⚡ Efficiency rules — read before doing anything

  1. Use the Read tool directly — never Bash cat or spawn Explore subagents for file reading
  2. Read everything in one parallel batch — each fast path lists the exact files; read them all at once in a single turn
  3. Run only the new test file during development — not the full package suite:
    NODE_OPTIONS="--experimental-vm-modules" npx jest --testPathPatterns="sap-[rule-name]" --no-coverage
    

Step 1 — Identify the rule type, then read the reference file

Type Use when Reference file
Annotation rule Validates UI.* OData annotations in .xml / .cds files. Also, covers rules where text, that is, a label, title, or description, can be an i18n binding references/annotation.md
Manifest JSON rule Validates manifest.json properties references/manifest-json.md
Flex change file rule Validates webapp/changes/*.change (Applicable only to OData V2 flex change properties) references/flex-change.md
JavaScript / TypeScript rule Validates JS/TS application source code (UI5 patterns, global variables, deprecated APIs) references/js-ts-rule.md

Infer from the request:

  • Rule name — sap-[kebab-case-name] pattern
  • OData version — V2 only, V4 only, or both
  • Page scope — which page types to check. Default: all page types (list report, object page, etc.) unless the spec explicitly restricts the scope. Do not limit to one page type based on the examples in the spec.
  • Auto-fix — yes/no
  • Severity — error or warn. Rules in recommended-for-s4hana MUST be warn.

OData version determines the linker file — always follow the stated version:

OData version Linker file Manifest root
V2 only src/project-context/linker/fe-v2.ts sap.ui.generic.app.pages.*
V4 only src/project-context/linker/fe-v4.ts sap.ui5.routing.targets.*
Both both linker files both roots

Read the full file on GitHub · 228 lines

Files

What ships with it

4 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.

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. 14d ago Changed · +5 lines 48fcc6a423c7
  2. 17d ago Changed · +1 lines 16dddc2936d0
  3. 1mo ago Changed · +5 lines f0f5d318c541
  4. 1mo ago First seen · 217 lines · 94 tokens per session scan A b359a0667508

Subscribe to this mod's changes

eslint-rule-development is a skill published in the GitHub repository SAP/open-ux-tools (159 stars, last pushed today), licensed Apache-2.0. It adds 94 tokens to every session and 3,020 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

code-review

Use when reviewing ABAP code, SAP development artifacts, CDS views, or any custom SAP code before transport release, pull request approval, or go-live sign-off.

vigneshbarani24/sap-superpowers · 36 tokens

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

ring:mapping-feature-relationships

Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…

LerianStudio/ring · 104 tokens