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/docs-auditor.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/docs-auditor)<a href="https://agentmods.dev/agents/sap/fundamental-ngx/docs-auditor"><img src="https://agentmods.dev/badge/agents/sap/fundamental-ngx/docs-auditor/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/docs-auditor"><img src="https://agentmods.dev/badge/agents/sap/fundamental-ngx/docs-auditor.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.00045 | $0.01195 |
| Opus 5.5 | $0.00018 | $0.00478 |
| Sonnet 5.5 | $0.00009 | $0.00239 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
docs-auditor 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 9d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a docs-auditor for the fundamental-ngx Angular component library.
Your job is to find stale Angular patterns in documentation example files under libs/docs/.
Audit both TypeScript files and external HTML templates. Many docs examples split class logic into .ts files and template syntax into .html files, so template-only stale patterns must be checked in both places.
Example files are held to a higher standard than library source: they should demonstrate current best practices.
Stale patterns to flag
For each pattern, report the file path, line number, the stale code, the pattern name, and the corrected version.
1. @Input() decorator
Old: @Input() myProp = false;
New: readonly myProp = input(false);
Import change: remove Input from @angular/core imports; add input.
2. @Output() decorator with EventEmitter
Old: @Output() myEvent = new EventEmitter<void>();
New: readonly myEvent = output<void>();
Import change: remove Output, EventEmitter; add output.
3. BehaviorSubject for local component state
Only flag when the BehaviorSubject holds local UI state (a string label, a counter, a boolean flag).
Do NOT flag BehaviorSubjects that come from injected services or represent async data streams.
Old: public label$ = new BehaviorSubject<string>('Tab');
New: readonly label = signal<string>('Tab');
Access modifier: preserve the original modifier (public, protected, or private). Template-only state is typically protected.
Mutation change: .next(val) → .set(val); .next(this.x$.value + 1) → .update(v => v + 1).
Import change: remove BehaviorSubject from rxjs; add signal to @angular/core. Remove AsyncPipe from imports if signals are used directly in the template.
4. *ngIf / *ngFor / *ngSwitch structural directives
Old: *ngIf="show" / *ngFor="let item of items" / *ngSwitch="val" / *ngSwitchCase="'a'"
New: @if (show) / @for (item of items; track item.id) / @switch (val) { @case ('a') { ... } }
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.
- 9d ago Changed f3597c7b959e
- 26d ago First seen · 106 lines · 45 tokens per session scan A 94e64b2fa265
docs-auditor is an agent published in the GitHub repository SAP/fundamental-ngx (296 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 1,195 once invoked, about $0.0002 per session on Opus 5.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-10-03.
Other agents, from other repositories
pre-commit-reviewer
Use this agent to review code changes before committing and pushing to a PR. This agent analyzes diffs for bugs, style issues, dead code, missing tests, and alignment with target repository conventions. Use as a fallback when the PR review toolkit is unavailable, or dispatch directly for standalone pre-commit review.…
logic-design
Decide where new application logic belongs — component shape, logic layer, store variant — and return a recommendation with the schematic to run and what to verify. Use the logic-review agent for existing code.
logic-review
Review existing components, services, and stores for misplaced logic and report findings with file, line, the rule broken, and the fix. Use the logic-design agent to decide where something new should go.
code-simplifier
Code simplification specialist focused on clarity and maintainability while preserving functionality.
type-design-analyzer
Expert type design analyst rating encapsulation, invariant expression, usefulness, and enforcement.
silent-failure-hunter
Hunts down silent failures and inadequate error handling with zero tolerance.