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-guidance-layoutgit 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-guidance-layout)<a href="https://agentmods.dev/skills/sap/fundamental-styles/component-guidance-layout"><img src="https://agentmods.dev/badge/skills/sap/fundamental-styles/component-guidance-layout.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.00025 | $0.03810 |
| Opus 5 | $0.00013 | $0.01905 |
| Sonnet 5 | $0.00005 | $0.00762 |
| Haiku 4.5 | $0.00003 | $0.00381 |
Grade A, and why
component-guidance-layout 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.
How it starts
The opening of the file, as written. The whole thing — 459 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Guidance - Layout & Containers
Layout structures and container components.
When to Use This Skill
Use this skill when:
- The user asks "Should I use [component] for [use case]?"
- The user needs to choose between similar components
- The user asks about component best practices
- The user wants to know when NOT to use a component
This skill covers: Action Bar, Bar, Card, Dynamic Page, Dynamic Side Content, Flexible Column Layout, Layout Panel, Panel, Settings, Tool Layout, Wizard
Action Bar
Description: The action bar displays at the top of the page, and includes the page's title, description, back button and action buttons. It provides page-level navigation and actions.
When to use:
- Display the page title and description at the top of the page
- Provide a back button for navigation to the previous page
- Show page-level action buttons that affect all items or the entire view
- Control settings of the UI that apply globally to the page
- Display actions at the top of the screen that are always visible
When to avoid:
- ❌ Finalizing actions at the bottom of the screen → Use
fd-barwith footer mode instead - ❌ Item-specific actions → Use
fd-toolbarfor item-level controls - ❌ Application-level navigation → Use
fd-shellbarinstead
Best practices:
- ✅ Use the
fd-titlecomponent with proper semantic heading levels (H1 styled as H3) - ✅ Include a back button on the left side for navigation hierarchy
- ✅ Place page title and description prominently
- ✅ Position primary actions on the right side
- ✅ Use
fd-button--emphasizedfor the primary page action - ✅ Keep action buttons concise and clearly labeled
- ✅ Make the action bar sticky (fixed to top) for long scrolling pages
- ⚠️ Limit the number of action buttons (3-5 maximum)
- ⚠️ For accessibility, the page title must be an H1 (use
fd-titlewith--h3for visual styling) - ❌ Don't duplicate actions that appear elsewhere on the page
Bar
Description: The bar is a container that can hold text, titles, buttons, and input elements. It provides a structured layout for page headers, subheaders, footers, and floating footers.
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 · 459 lines · 25 tokens per session scan A 154ff972bb8a
component-guidance-layout is a skill published in the GitHub repository SAP/fundamental-styles (232 stars, last pushed 4d ago), licensed Apache-2.0. It adds 25 tokens to every session and 3,810 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
visualize
Render a polished visual inline in the chat as part of your answer — a diagram, a chart, an interactive explainer, or a UI mockup. Load it proactively whenever an explanation would land better as a picture than as prose. Do not wait to be asked.
vellum-workspace-theme
Customize the app's visual theme — author design-token overrides (accent, background, surfaces, text, message-bubble colors) in the workspace ui/theme.json, validated by the assistant runtime and applied live to connected clients. Covers the token slots, the all-or-none override groups, the contrast floor, and reading…
vellum-avatar
Customize the assistant's avatar - build a native character, upload an image, or generate one with AI.
shieldcn-badges
Create polished shieldcn README badges, badge groups, charts, headers, sponsors grids, and full README hero sections. Use when a user wants shadcn/ui-styled badges, Shields.io replacement, npm/GitHub/CI/status badges, download charts, README header banners, contributor/sponsor images, or README Studio guidance.…
openscreen-design
Use this skill to generate well-branded interfaces and assets for OpenScreen (an AI-native screen-recording studio & video editor), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.
figma-expert
Figma design expert for components, auto-layout, design systems, and developer handoff.