hana-developer-cli-tool-example sapui5-ui-development.instructions.md

Development rules for SAPUI5 user interfaces in the app/resources/ folder. SAPUI5 is a JavaScript framework for building business applications, including interfaces that follow SAP's Fiori design system.

In plain words
What is it for?
Use them when building or updating SAPUI5 screens, controllers, views, shared UI components, internationalized text, responsive layouts, or dark and Fiori 3 themes.
Why use it?
They keep components, controllers, views, translations, models, themes, and responsive behavior consistent across the application.

Instructions file for GitHub Copilot

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 instructions/sap-samples/hana-developer-cli-tool-example/sapui5-ui-development
Clone the repo
git clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-example

Made for: GitHub Copilot.

Per session 6,791 This file is loaded in full into every session.
When invoked 6,791 The same file — it is already loaded in full.
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.06791 $0.06791
Opus 5 $0.03395 $0.03395
Sonnet 5 $0.01358 $0.01358
Haiku 4.5 $0.00679 $0.00679

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

Security

Grade A, and why

hana-developer-cli-tool-example sapui5-ui-development.instructions.md 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 2d 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.

.github/instructions/sapui5-ui-development.instructions.md · 942 lines

How it starts

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

SAPUI5 UI Development Guidelines

Use this guide when creating or modifying SAPUI5 user interfaces in the app/resources/ directory.

Scope and Purpose

This guide applies to all UI components in app/resources/. Each feature area (e.g., systemInfo, inspect, tables) is a self-contained SAPUI5 application that follows common patterns and extends shared base components from app/resources/common/.

Critical Principles

  1. Consistency: All UI components follow the same structural pattern and inheritance model.
  2. Reusability: Extend sap.hanacli.common.controller.BaseController for all controllers.
  3. Internationalization: All user-facing text comes from i18n resource bundles.
  4. Type Safety: Use JSDoc comments and structured error handling.
  5. Shared Resources: Leverage common fragments, models, and utilities.
  6. Responsive Design: Support desktop, tablet, and phone device types.
  7. Theme Support: Include dark mode detection and Fiori 3 theme variants.
  8. Namespace Convention: All components use sap.hanacli.* namespace.

Folder Structure Template

Each UI component follows this structure:

app/resources/<featureName>/
├── Component.js           # Component definition extending common.Component
├── manifest.json          # Application descriptor with routing, models, i18n
├── index.html             # Bootstrap HTML with UI5 CDN and dark mode detection
├── controller/
│   └── App.controller.js  # Main controller extending BaseController
└── view/
    └── App.view.xml       # Main view with responsive layout

Component Definition (Component.js)

Every component extends the common base component:

sap.ui.define([
    "sap/hanacli/common/Component"
], function (UIComponent) {
    "use strict";

    return UIComponent.extend("sap.hanacli.<featureName>.Component", {

        metadata: {
            manifest: "json"
        },

        init: function () {
            this.superInit();
        }
    });
});

Read the full file on GitHub · 942 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. 2d ago First seen · 942 lines · 6,791 tokens per session scan A c90acabaea5b

Subscribe to this mod's changes

hana-developer-cli-tool-example sapui5-ui-development.instructions.md is an instructions file published in the GitHub repository SAP-samples/hana-developer-cli-tool-example (109 stars, last pushed 7d ago), licensed Apache-2.0. It adds 6,791 tokens to every session, about $0.0340 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.