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 agentmods add instructions/radu103/github-copilot-vscode-sap-dev-instructions/2-sap-uigit clone --depth 1 https://github.com/radu103/github-copilot-vscode-sap-dev-instructionsWrote 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/radu103/github-copilot-vscode-sap-dev-instructions/2-sap-ui)<a href="https://agentmods.dev/instructions/radu103/github-copilot-vscode-sap-dev-instructions/2-sap-ui"><img src="https://agentmods.dev/badge/instructions/radu103/github-copilot-vscode-sap-dev-instructions/2-sap-ui.svg" alt="Measured on agentmods" 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 | $0.00392 | $0.00392 |
| Opus 5 | $0.00196 | $0.00196 |
| Sonnet 5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
github-copilot-vscode-sap-dev-instructions 2-sap-ui.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 4d 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.
What it actually says
SAP UI5 Frontend Rules
- Use the latest stable SAP UI5 LTS version patch: >=1.136.14
- Getting started help for SAP UI5: https://sapui5.hana.ondemand.com/1.71.73/#/topic/8b49fc198bf04b2d9800fc37fecbb218
- Cross-check with SAP UI5 samples: https://sapui5.hana.ondemand.com/#/api
- SAP UI5 API Documentation: https://sapui5.hana.ondemand.com/1.136.14/#/api
- SAP Fiori floorplans for common types of pages: https://www.sap.com/design-system/fiori-design-web/v1-142/page-types/floorplans/when-to-use-which-floorplan
Naming conventions
- Always use Hungarian notation for all names of variables and properties.
- For functions, use the camelCase notation.
- For routes, views, and targets in manifest.json, use a capital first letter.
- For variable declaration use
letinstead ofvar
Frontend rules
- Use a UI5 freestyle application, not Fiori extensions.
- Always use the BaseController.js pattern for reusable controller functions when needed in multiple controllers
- All lists/tables are of type sap.m.Table with filters for all associations and own date fields.
- Own app UI annotations live in each ui app/* folder and are projections on backend srv/ services.
- When a custom action or function is needed, the implementation is made only on backend srv/ services, not in ui app/*.
- All texts are maintained in i18n model language files.
- All formatters are in a separate formatter.js file in each ui app/* folder.
Frontend testing rules
- No tests for UI5 controller functions.
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.
- 4d ago First seen · 31 lines · 392 tokens per session scan A dae408f9975e
github-copilot-vscode-sap-dev-instructions 2-sap-ui.instructions.md is an instructions file published in the GitHub repository radu103/github-copilot-vscode-sap-dev-instructions (8 stars, last pushed 3mo ago), licensed MIT. It adds 392 tokens to every session, about $0.0020 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-31.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.