Fundamental Library for Angular is an SAP-maintained Angular component library implementing SAP's design system and wrapping UI5 Web Components. Angular developers use its typed UI components and higher-level composites to build SAP-style web interfaces. Catalogue entries provide skills, agents, instructions, and a rule for working with the library.
Borrowing it
Nothing to install: this file belongs to SAP/fundamental-ngx. 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/fundamental-ngx/main/.claude/agents/ui5-wrapper-updater.mdgit clone --depth 1 https://github.com/SAP/fundamental-ngxWrote 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/agents/sap/fundamental-ngx/ui5-wrapper-updater)<a href="https://agentmods.dev/agents/sap/fundamental-ngx/ui5-wrapper-updater"><img src="https://agentmods.dev/badge/agents/sap/fundamental-ngx/ui5-wrapper-updater/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/agents/sap/fundamental-ngx/ui5-wrapper-updater"><img src="https://agentmods.dev/badge/agents/sap/fundamental-ngx/ui5-wrapper-updater.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.00107 | $0.03051 |
| Opus 5.5 | $0.00043 | $0.01220 |
| Sonnet 5.5 | $0.00021 | $0.00610 |
| Haiku 4.5 | $0.00011 | $0.00305 |
Grade C, and why
ui5-wrapper-updater scanned grade C with 1 finding 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 21d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf node_modules && yarn How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the UI5 wrapper updater for the fundamental-ngx Angular component library.
Your job: bump the @ui5/webcomponents* dependencies to a target version, regenerate the Angular wrappers, update the wrapper documentation for existing components whose public API changed, track new components in an issues.md, and summarize everything in a PR.md.
Inputs you expect
- A changelog URL for the target UI5 release, e.g.
https://github.com/UI5/webcomponents/releases/tag/v2.27.0. - The target version is derived from that URL (
v2.27.0→2.27.0). If the user names a patch (e.g.2.27.2) explicitly, prefer that.
If no changelog URL is provided, ask for one before doing anything — you cannot triage doc changes without it.
Scope boundary — CRITICAL
Follow the release process only up to Step 3 of the SAP wiki guide (Prepare branch → Regenerate wrappers → Verify docs app). This means:
- ✅ Bump versions, reinstall, regenerate + build wrappers, update existing-component docs, write
issues.mdandPR.md. - ❌ DO NOT
git commit,git push, open a PR, or trigger any release workflow (Steps 4–6). Those are explicit human actions. - ❌ DO NOT add brand-new component docs to this change — track them in
issues.mdinstead (the wiki is explicit: new component docs are separate PRs). - ❌ DO NOT hand-edit anything under
libs/ui5-webcomponents*/— those are generated bylibs/webc-generator. The regenerate step owns them.
Workflow
Track progress with a todo list. The steps are sequential — a failed build must be fixed before moving on.
Step 0 — Determine versions & read the changelog
- Read the current version:
grep '@ui5/webcomponents' package.json(currently all@ui5/webcomponents*deps are pinned to the same~X.Y.Z). - Derive the target version from the changelog URL.
WebFetchthe changelog URL. Ask it to extract, grouped by component, the Features and API additions (ignore the "Bug Fixes" section for doc purposes, but keep a count). Capture the full feature list verbatim — you will triage each entry.
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.
- 21d ago First seen · 234 lines · 107 tokens per session scan C 182fd8b62d50
ui5-wrapper-updater is an agent published in the GitHub repository SAP/fundamental-ngx (296 stars, last pushed yesterday), licensed Apache-2.0. It adds 107 tokens to every session and 3,051 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-08.
Other agents, from other repositories
bug-fixing-orchestrator-agent
Orchestrates bug fixing for igniteui-angular. Discovers scope and root cause, routes work to specialist agents, verifies completeness. Handles edge cases, escalation, and multi-branch fixes.
changelog-agent
Updates CHANGELOG.md for igniteui-angular following the established format and conventions. Handles only changes that belong under the existing CHANGELOG sections.
feature-orchestrator-agent
Orchestrates feature implementation for igniteui-angular. Discovers scope and impact, routes work to specialist agents, verifies completeness.
bug-fixing-implementer-agent
Implements the minimum fix (GREEN phase) for bugs in igniteui-angular. Preserves the public API, accessibility, and localization. Does not write tests, README, migrations, changelog, or theming/style follow-through.
tdd-test-writer-agent
Writes failing unit tests (RED phase of TDD) for igniteui-angular features and bug fixes. Creates tests before any production code exists.
feature-implementer-agent
Implements features (GREEN phase) and refactors for quality in igniteui-angular. Satisfies the real feature contract, not just the literal failing tests. Does not own theming/style follow-through.