Fundamental Library Styles is a framework-independent CSS component library for creating SAP web interfaces with reusable styles and components. Developers can use it with Angular, React, Vue, or plain HTML to build consistent SAP applications and apply supported visual themes.
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 skills add SAP/fundamental-styles --skill component-docsgit clone --depth 1 https://github.com/SAP/fundamental-stylesWrote 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-styles/component-docs)<a href="https://agentmods.dev/skills/sap/fundamental-styles/component-docs"><img src="https://agentmods.dev/badge/skills/sap/fundamental-styles/component-docs/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/skills/sap/fundamental-styles/component-docs"><img src="https://agentmods.dev/badge/skills/sap/fundamental-styles/component-docs.svg" alt="Reviewed on agentmods" width="80" 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.00083 | $0.01854 |
| Opus 5.5 | $0.00033 | $0.00742 |
| Sonnet 5.5 | $0.00017 | $0.00371 |
| Haiku 4.5 | $0.00008 | $0.00185 |
Grade A, and why
component-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 1mo 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Documentation Browser
This skill provides access to comprehensive component documentation for fundamental-styles, SAP's CSS component library. Each component's documentation includes complete HTML examples with all variants, modifiers, states, and proper ARIA attributes extracted from Storybook stories.
When to Use This Skill
Use this skill when the user:
- Asks for HTML examples of any fundamental-styles component
- Needs to see all variants/modifiers for a component (e.g., "show me all button types")
- Wants working, copy-paste-ready HTML code
- Mentions Storybook examples or stories
- Asks "how do I use component X?"
- Needs to understand component structure and nesting
- References specific components by name (button, table, dialog, input, etc.)
How to Access Component Documentation
There are multiple ways to retrieve component documentation:
Method 1: Read Markdown Files Directly
The documentation lives in docs/components/ with one markdown file per component:
docs/components/button.md
docs/components/table.md
docs/components/input.md
docs/components/dialog.md
When to use: The user asks for a specific component by name, or you need complete documentation including frontmatter metadata.
Read the file and extract:
- Frontmatter (component name, selector, CSS file, category)
- All HTML examples with their headings
- Modifier descriptions
Method 2: Use MCP Tool (if available)
If you have access to the fundamental-styles MCP server, use the get_component_markdown tool:
get_component_markdown("button")
→ Returns structured JSON with all examples
get_component_markdown("input", examplesOnly: true)
→ Returns just the HTML code blocks
When to use: MCP server is available and you need structured programmatic access to the documentation.
Method 3: Browse the Component Index
Read docs/components/README.md to see all 140+ available components organized by category. Use this when the user asks "what components are available for X?" or needs to discover which component to use.
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.
- 1mo ago First seen · 199 lines · 83 tokens per session scan A f43cc8c5b66b
component-docs is a skill published in the GitHub repository SAP/fundamental-styles (236 stars, last pushed 4d ago), licensed Apache-2.0. It adds 83 tokens to every session and 1,854 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
static-web-artifacts-builder
Build self-contained static HTML artifacts opened in a browser: interactive diagrams, dashboards, infographics. Pure HTML5+CSS3+inline SVG, zero toolchain. Triggers on: "interactive HTML", "open in browser", "HTML artifact", "visual dashboard", "HTML infographic". NOT for PNG/SVG output, use concept-to-image.
make-interfaces-feel-better
Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel…
grainient
Recreate grainient.supply's 16 dark-mode visual effects as single-file HTML pages: WebGL shader gradients, vignette overlays, 9-layer box shadows, smooth scroll, spring animations, hover-zoom, ticker marquees, glassmorphism, 3D card flips, bento grids, gradient CTAs. Dark-mode-first with lime green (#C2F13C) accent.…
figma-mcp
Convert Figma designs into production-ready code using MCP server tools. Use this skill when users provide Figma URLs, request design-to-code conversion, ask to implement Figma mockups, or need to extract design tokens and system values from Figma files. Works with frames, components, and entire design files to…
shadcn
Install, customize, and compose shadcn/ui components with design-system awareness. Covers CLI v4, custom registries, Tailwind v4 OKLCH theming, components.json, presets, and monorepo setup. Pairs with minoan-frontend-design for creative direction. Triggers on shadcn, install component, shadcn theme, OKLCH colors…
kortix-genui
Renders rich UI in the Kortix web and mobile chat: step rows with photos, option cards, checklists, maps, image galleries, tables, charts, stat rows, comparisons. Load it FIRST, before you answer, when the user asks for: a guide, how-to or first-time process done in the real world (a trip, a flight, a visa, a recipe…