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/sap/open-ux-tools/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.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.07818 | $0.07818 |
| Opus 5 | $0.03909 | $0.03909 |
| Sonnet 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 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.
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.
- 4d 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 (155 stars, last pushed 2d ago), licensed Apache-2.0. It adds 7,818 tokens to every session, about $0.0391 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.
Other instructions, from other repositories
abap2UI5 AGENTS.md
Instructions for abap2UI5/abap2UI5, covering agents.md — ai assistant guide for abap2ui5, where knowledge lives, project overview, related repositories and architecture.
abap2UI5 CLAUDE.md
Instructions for abap2UI5/abap2UI5: All project guidance lives in AGENTS.md — the single source of truth for this repository (architecture and the layered design, the src/00-99 packages, the generated app/webapp mirror, the build and delivery pipeline, the CI gates and ABAP code style).
samples CLAUDE.md
Instructions for abap2UI5/samples: All project guidance now lives in AGENTS.md — the single source of truth for this repository (folder scheme, src/01 vs src/00 compatibility model, overview generation rules, ABAP code style, and app structure).
sap-superpowers CLAUDE.md
Claude Code instructions for vigneshbarani24/sap-superpowers, covering sap superpowers v3.1, skills (53+), meta skills (5), consulting skills (9) and development skills (8).
samples AGENTS.md
Instructions for abap2UI5/samples, covering agents.md, language, pull requests, 1. repository layout and the restricted and obsolete packages are gone.
capforge CLAUDE.md
Claude Code instructions for automatizatodo/capforge, covering capforge — project context, rules, architecture and verify.