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/skills/preflight/SKILL.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/skills/sap/fundamental-ngx/preflight)<a href="https://agentmods.dev/skills/sap/fundamental-ngx/preflight"><img src="https://agentmods.dev/badge/skills/sap/fundamental-ngx/preflight.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00011 | $0.00499 |
| Opus 5 | $0.00005 | $0.00249 |
| Sonnet 5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
preflight 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 8d 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.
What it actually says
Preflight Check
Run all local quality gates for the affected library. If no argument provided, detect the library from changed files via git diff --name-only.
Steps
1. Identify scope
# If $ARGUMENTS provided, use it. Otherwise detect from changed files:
git diff --name-only HEAD~1
Map changed file paths to library names (libs/core/ → core, libs/platform/ → platform, etc.).
2. Format
yarn format
Ensure all code is formatted before running quality gates.
3. Build
nx run <library>:build
Report: PASS or FAIL with error summary.
4. Lint
nx run <library>:lint
Report: PASS or FAIL with violation count and top issues.
5. Unit tests
nx run <library>:test --skip-nx-cache
Report: PASS or FAIL with failing test names and error messages.
6. Export check
For each changed component file, verify it is exported from the library's public_api.ts or index.ts. Flag any new public classes missing from exports.
7. Breaking change check
Run git diff on changed files. Flag:
- Removed
input(),output(), ormodel()declarations - Renamed exported classes, functions, or types
- Changed input/output names
- Changed default values
If breaking changes found, verify the commit message contains BREAKING CHANGE: footer.
Output
## Preflight Report
| Gate | Status | Details |
|-------------------|--------|------------------|
| Format | PASS | |
| Build | PASS | |
| Lint | FAIL | 3 violations |
| Unit Tests | PASS | 42 tests passed |
| Exports | PASS | |
| Breaking Changes | WARN | 1 input removed |
### Failures
[details for each failed gate]
### Action Required
[what needs fixing before PR]
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.
- 8d ago First seen · 92 lines · 11 tokens per session scan A e48452df8100
preflight is a skill published in the GitHub repository SAP/fundamental-ngx (294 stars, last pushed 2d ago), licensed Apache-2.0. It adds 11 tokens to every session and 499 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…