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 agents/sap/fundamental-ngx/breaking-changesgit clone --depth 1 https://github.com/SAP/fundamental-ngxWhat 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 | $0.00000 | $0.01949 |
| Opus 5 | $0.00000 | $0.00975 |
| Sonnet 5 | $0.00000 | $0.00390 |
| Haiku 4.5 | $0.00000 | $0.00195 |
Grade A, and why
breaking-changes 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 2d 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Breaking Changes & Dead Code Removal
This document covers guidelines for identifying breaking changes and safely removing dead code.
Table of Contents
- What Constitutes a Breaking Change
- Breaking Change Commit Format
- Before Removing Public API
- Dead Code Removal
- Common Dead Code Patterns
- Documentation File Guidelines
What Constitutes a Breaking Change
A breaking change is any modification that could cause existing consumer code to fail or behave differently after upgrading.
| Change Type | Breaking? | Example |
|---|---|---|
| Removing exported class/function/type | ✅ Yes | Removing DestroyedService from public API |
| Removing exported constant/token | ✅ Yes | Removing FD_BUTTON InjectionToken |
| Changing function signature | ✅ Yes | Adding required parameter, changing return type |
| Renaming exported symbol | ✅ Yes | Renaming ButtonComponent to FdButton |
| Changing input/output names | ✅ Yes | Renaming @Input() label to @Input() text |
| Changing default values | ⚠️ Maybe | If consumers rely on the default behavior |
| Adding optional parameter | ❌ No | Adding options?: Config parameter |
| Adding new export | ❌ No | Exporting new CardComponent |
| Internal refactoring | ❌ No | Changing private implementation details |
Breaking Change Commit Format
fix(scope)!: description of change
BREAKING CHANGE: Detailed explanation of what changed and migration path.
Key points:
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.
- 2d ago First seen · 254 lines · 0 tokens per session scan A a30b447c669a
breaking-changes is an agent published in the GitHub repository SAP/fundamental-ngx (294 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,949 tokens. 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 agents, from other repositories
primitive-reviewer
Reviews an Angular headless primitive against WAI-ARIA spec, Base UI parity, Angular signals best practices, and Radix NG project conventions. Returns a prioritized list of issues.
primitive-builder
Implements a new Angular headless primitive following all Radix NG conventions. Use when asked to create a new primitive from scratch or add missing parts to an existing one.
external-scale
External scale renderer and bar/gauge wrappers.
a11y
Accessibility (WCAG 2.1 AA + 2.2 § 2.5.8 target size) — keyboard nav, ARIA, focus.
automation-components
Automation devices, valves, lines, tanks, badges.
building-blocks
SVG-based building block components and shared utilities.