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/update-docsnpx skills add SAP/fundamental-ngx --skill update-docsgit 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/update-docs)<a href="https://agentmods.dev/skills/sap/fundamental-ngx/update-docs"><img src="https://agentmods.dev/badge/skills/sap/fundamental-ngx/update-docs.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.00688 |
| Opus 5 | $0.00009 | $0.00344 |
| Sonnet 5 | $0.00003 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
update-docs 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Documentation: $ARGUMENTS
If $ARGUMENTS is empty, ask the user for a component path or folder before proceeding.
Verify that documentation examples are in sync with the component's current public API. If a path to a component is given, find its corresponding docs. If a docs path is given, find the component it documents.
Phase 1: Map component to docs
Component locations: libs/core/<component>/ or libs/platform/<component>/
Docs locations: libs/docs/core/<component>/ or libs/docs/platform/<component>/
Read:
- The component
.tsfile — extract allinput(),output(),model(),@Input(),@Output()declarations - The docs component (e.g.
<component>-docs.component.tsand.html) - All example files in the docs
examples/folder
Phase 2: Audit
API coverage
For each public input/output/model on the component:
- Is it demonstrated in at least one example?
- Is it mentioned in a
<description>block? - If it has non-obvious behavior, is there a dedicated section?
Flag inputs/outputs that exist in the component but are not documented anywhere.
Example quality
For each example file:
- Individual component imports — no deprecated
*Moduleclasses -
@fundamental-styles/common-cssutility classes — no inline styles where avoidable - Every demonstrated feature is user-observable
- No unnecessary standalone examples (consolidate where possible)
- Example code matches current API (no removed/renamed inputs)
Description accuracy
For each <description> block in the docs HTML:
- Input/output names in
<code>tags match the actual component API - Described behavior matches the component's implementation
- No references to removed or renamed APIs
Phase 3: Fix
For each issue found:
- Missing documentation — Add the input/output to an existing example's description, or add it to an existing example template if it can be demonstrated inline
- Stale references — Update
<code>tags and descriptions to match current API - Convention violations — Replace deprecated module imports, replace inline styles with common-css classes
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 · 91 lines · 17 tokens per session scan A 43b1969b0f8c
update-docs is a skill published in the GitHub repository SAP/fundamental-ngx (294 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 688 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.
ng-blatui
Use the ng-blatui Angular UI library in an app — install, import components (bui-prefixed, signal-based, zoneless, SSR-safe), theme with Tailwind v4 + oklch tokens, localize dates/numbers/labels, and discover the full catalog via the registry, api.json, llms.txt or the ng-blatui-mcp MCP server. Invoke when building…
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…