Borrowing it
Nothing to install: this file belongs to SAP-samples/hana-developer-cli-tool-example. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SAP-samples/hana-developer-cli-tool-example/main/.github/instructions/sapui5-ui-development.instructions.mdgit clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-exampleWrote 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/instructions/sap-samples/hana-developer-cli-tool-example/sapui5-ui-development)<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/sapui5-ui-development"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/sapui5-ui-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.
<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/sapui5-ui-development"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/sapui5-ui-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.06791 | $0.06791 |
| Opus 5.5 | $0.02716 | $0.02716 |
| Sonnet 5.5 | $0.01358 | $0.01358 |
| Haiku 4.5 | $0.00679 | $0.00679 |
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 1mo 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 — 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
- Consistency: All UI components follow the same structural pattern and inheritance model.
- Reusability: Extend
sap.hanacli.common.controller.BaseControllerfor all controllers. - Internationalization: All user-facing text comes from i18n resource bundles.
- Type Safety: Use JSDoc comments and structured error handling.
- Shared Resources: Leverage common fragments, models, and utilities.
- Responsive Design: Support desktop, tablet, and phone device types.
- Theme Support: Include dark mode detection and Fiori 3 theme variants.
- 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();
}
});
});
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.
- 1mo ago First seen · 942 lines · 6,791 tokens per session scan A c90acabaea5b
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 (114 stars, last pushed 11d ago), licensed Apache-2.0. It adds 6,791 tokens to every session, about $0.0272 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.