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-feedbackgit 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-feedback)<a href="https://agentmods.dev/skills/sap/fundamental-styles/component-guidance-feedback"><img src="https://agentmods.dev/badge/skills/sap/fundamental-styles/component-guidance-feedback/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-guidance-feedback"><img src="https://agentmods.dev/badge/skills/sap/fundamental-styles/component-guidance-feedback.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.00024 | $0.04963 |
| Opus 5 | $0.00012 | $0.02482 |
| Sonnet 5 | $0.00005 | $0.00993 |
| Haiku 4.5 | $0.00002 | $0.00496 |
Grade A, and why
component-guidance-feedback 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 — 595 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Guidance - Feedback & Status
Components for user feedback, messages, and status indication.
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 Sheet, Busy Indicator, Contextual Menu, Message Box, Message Page, Message Popover, Message Strip, Message Toast, Notification, Popover, Progress Indicator, Quick View, Rating Indicator, Skeleton, Status Indicator
Action Sheet
Description: An action sheet consists of a list of options a user can select from to complete an action. Actions can be clustered if there is not enough space on the screen. Action sheets are typically used on mobile devices.
When to use:
- You need an option that provides more than one action
- It is really important that the user stays in context on a phone
- You only have a small number of actions (typically 3-8)
- You want a mobile-optimized action menu
- You need a touch-friendly interface for selecting from multiple options
- You want to display actions in a bottom sheet on mobile devices
When to avoid:
- ❌ The menu provides only one option → Use a button instead
- ❌ You need to show a hierarchical menu → Use
fd-menubutton instead - ❌ Desktop applications → Use
fd-menuorfd-popoverinstead for better desktop UX - ❌ Your users would benefit more from a split button → Use
fd-split-buttonwhich offers an easy-to-access default action with additional options
Best practices:
- ✅ Use action sheets primarily for mobile/touch interfaces
- ✅ Keep the number of actions manageable (3-8 options)
- ✅ Use clear, action-oriented labels (verbs like "Share", "Delete", "Copy")
- ✅ Place destructive actions at the bottom with visual distinction (red color)
- ✅ Always include a "Cancel" option to dismiss the action sheet
- ✅ Make touch targets large enough (minimum 44x44 pixels)
- ✅ Use icons alongside text for better scannability
- ⚠️ On desktop, consider using a menu or popover instead
- ⚠️ Don't use action sheets for complex nested menus
- ❌ Don't use for single actions (just use a button)
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 First seen · 595 lines · 24 tokens per session scan A 95c20d297cb5
component-guidance-feedback is a skill published in the GitHub repository SAP/fundamental-styles (232 stars, last pushed 5d ago), licensed Apache-2.0. It adds 24 tokens to every session and 4,963 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.