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-styles/component-docsnpx skills add SAP/fundamental-styles --skill component-docsgit clone --depth 1 https://github.com/SAP/fundamental-stylesWhat 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.00083 | $0.01854 |
| Opus 5 | $0.00042 | $0.00927 |
| Sonnet 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 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 — 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.
- 2d 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 (232 stars, last pushed 4d ago), licensed Apache-2.0. It adds 83 tokens to every session and 1,854 once invoked, about $0.0004 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
frontend-v2-theming
Theming, design tokens, colors, and visual language in the RomM v2 frontend. Use when styling v2 components, picking colors, adding/using CSS variables, working with light/dark themes, or whenever you'd reach for a hex/rgba literal. Covers the token pipeline (src/v2/tokens/index.ts → build:tokens → tokens.css), the…
design-guide
GitMesh Agents UI design system. Invoke this skill when creating new components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language. Covers component creation, design tokens, typography, status/priority systems, composition…
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states.…
minoan-frontend-design
Build distinctive, production-grade frontend interfaces — websites, landing pages, dashboards, React components, HTML/CSS layouts, editorial heroes with depth-parallax (Astryx pattern), pointer-reactive fluid effects, pixel-glitch canvas heroes and terminal-style tool-panel dioramas (Composio pattern). Avoids generic…
accessibility-compliance
Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.
redesign-codex-ui
Redesign and locally modify an existing Codex desktop or web interface from reference images, a user persona, a celebrity, idol, actor, musician, fictional character or original IP theme, a visual style, or a combination of these inputs. Use when Codex needs to inspect a local Codex installation or source checkout…