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.
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.
curl -O https://raw.githubusercontent.com/SAP/open-ux-tools/main/AGENTS.mdgit clone --depth 1 https://github.com/SAP/open-ux-toolsWrote 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/open-ux-tools/agents-md)<a href="https://agentmods.dev/instructions/sap/open-ux-tools/agents-md"><img src="https://agentmods.dev/badge/instructions/sap/open-ux-tools/agents-md/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/open-ux-tools/agents-md"><img src="https://agentmods.dev/badge/instructions/sap/open-ux-tools/agents-md.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.07818 | $0.07818 |
| Opus 5.5 | $0.03127 | $0.03127 |
| Sonnet 5.5 | $0.01564 | $0.01564 |
| Haiku 4.5 | $0.00782 | $0.00782 |
Grade A, and why
open-ux-tools AGENTS.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 — 895 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Guidelines for SAP UX Tools
This document provides essential guidelines for AI-powered tools working with the SAP UX Tools monorepo. Following these guidelines ensures code quality, maintainability, and consistency across the project.
Table of Contents
- Overview
- AI Agent Behavior
- Critical Requirements
- Quality Gates
- Development Standards
- Package Management
- Testing Requirements
- Security and Maintenance
- Change Management
- Useful Commands
Overview
The SAP UX Tools is a monorepo for building SAP Fiori applications. All packages of this monorepo can be found in the /packages folder. The project uses:
- Package Manager: pnpm (see root package.json for required version)
- Node Version: >=20.x (see root package.json engines field)
- Build System: Nx for orchestration
- Testing: Jest for unit tests, Playwright for integration tests
- Versioning: Changesets for automated version management
- Publishing: Automated via GitHub Actions to npmjs.com
AI Agent Behavior
Think Before Coding
Don't assume. Don't hide confusion. Surface tradeoffs.
Before implementing:
- State your assumptions explicitly. If uncertain, ask.
- If multiple interpretations exist, present them - don't pick silently.
- If a simpler approach exists, say so. Push back when warranted.
- If something is unclear, stop. Name what's confusing. Ask.
- If mid-task you discover the goal was wrong (e.g. the real issue is elsewhere), stop. Restate the correct goal and confirm before continuing — don't finish the wrong task just because you started it.
Surgical Changes
Touch only what you must. Clean up only your own mess.
When editing existing code:
- Don't "improve" adjacent code, comments, or formatting.
- Don't refactor things that aren't broken.
- Match existing style, even if you'd do it differently.
- If you notice unrelated dead code, mention it - don't delete it.
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 · 895 lines · 7,818 tokens per session scan A 325edfb3e6fd
open-ux-tools AGENTS.md is an instructions file published in the GitHub repository SAP/open-ux-tools (159 stars, last pushed today), licensed Apache-2.0. It adds 7,818 tokens to every session, about $0.0313 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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
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).