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.
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 skills/sap/fundamental-ngx/migratenpx skills add SAP/fundamental-ngx --skill migrategit 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/skills/sap/fundamental-ngx/migrate)<a href="https://agentmods.dev/skills/sap/fundamental-ngx/migrate"><img src="https://agentmods.dev/badge/skills/sap/fundamental-ngx/migrate.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.1 | $0.00017 | $0.01510 |
| Opus 5 | $0.00009 | $0.00755 |
| Sonnet 5 | $0.00003 | $0.00302 |
| Haiku 4.5 | $0.00002 | $0.00151 |
Grade A, and why
migrate 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 6d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular 22+ Migration: $ARGUMENTS
If $ARGUMENTS is empty, ask the user for a component path or folder before proceeding.
Phase 1: Analyze
Read all files in the target path. For each component, directive, or service, scan for migration items below. If a folder is given, process all .ts and .html files within it.
What to migrate
Inputs / Outputs / Models:
@Input()→input()orinput.required()@Input()with setter →input()+linkedSignal()(preferred) oreffect()(only for DOM side effects)@Input()+@Output()pair (e.g.value/valueChange) →model()@Output()→output()- Boolean inputs: add
{ transform: booleanAttribute } - Number inputs: add
{ transform: numberAttribute }
Host bindings:
@HostBinding('class.x')→host: { '[class.x]': 'expr()' }@HostBinding('attr.x')→host: { '[attr.x]': 'expr()' }@HostBinding('style.x')→host: { '[style.x]': 'expr()' }@HostListener('event')→host: { '(event)': 'handler($event)' }
Queries:
@ViewChild()→viewChild()orviewChild.required()@ViewChildren()→viewChildren()@ContentChild()→contentChild()@ContentChildren()→contentChildren()
Template syntax:
*ngIf→@if*ngFor→@for(requirestrackexpression)*ngSwitch/*ngSwitchCase→@switch/@case
State management:
BehaviorSubjectused for local component state →signal()BehaviorSubject+combineLatest→computed()Subject<void>used only to trigger side effects →effect()effect()that only callssignal.set()for derived state →computed()orlinkedSignal- Redundant
markForCheck()after signal updates → remove - Object/array mutation in place +
signal.set()with same ref → immutable update withsignal.update()
CSS class building:
CssClassBuilder+@applyCssClass→computed()returning class string +host: { '[class]': '_cssClass()' }
Cleanup patterns:
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.
- 6d ago First seen · 160 lines · 17 tokens per session scan A bac1578357e5
migrate is a skill published in the GitHub repository SAP/fundamental-ngx (294 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 1,510 once invoked, about $0.0001 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 skills, from other repositories
angular-best-practices
Official Angular v22 coding best practices — signals, standalone, native control flow, zoneless, host bindings, Signal Forms, inject(), and accessibility (WCAG AA / AXE). Use whenever writing, generating, or reviewing Angular/TypeScript code in this repo.
neuralng-angular
Build or update Angular 22+ interfaces with NeuralNg when exact component selection, imports, forms, accessibility, SSR, icons, or theming guidance is needed.
igniteui-angular-figma-to-app
Translate Figma app screens designed using the Indigo.Design UI Kits into production Angular applications with Ignite UI for Angular. The Indigo.Design UI Kits are Figma component libraries available in four design-system variants — Material, Fluent, Bootstrap, and Indigo — each with light and dark themes. Designers…
igniteui-angular-generate-from-image-design
Implement Angular application views from design images using Ignite UI Angular components. Uses MCP servers (igniteui-cli, igniteui-theming, angular-cli) to discover components, generate themes, and follow best practices. Triggers when the user provides a design image (screenshot, mockup, wireframe) and wants it built…
igniteui-angular-theming
Generates and customizes Ignite UI for Angular themes including color palettes, typography, elevations, and component-level styles using the Sass theming system and the igniteui-theming MCP server. Use when users ask to theme, restyle, or style Ignite UI components, change colors or the color palette, switch between…
igniteui-angular-grids
Provides guidance on all Ignite UI for Angular data grid types (Flat Grid, Tree Grid, Hierarchical Grid, Grid Lite, Pivot Grid) including setup, column configuration, sorting, filtering, selection, editing, grouping, summaries, toolbar, export, paging, remote data, and state persistence. Use when users ask about…