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 andrewsrigom/agent-skills --skill lucide-react-overview-and-setupgit clone --depth 1 https://github.com/andrewsrigom/agent-skillsWrote 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/andrewsrigom/agent-skills/lucide-react-overview-and-setup)<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/lucide-react-overview-and-setup"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/lucide-react-overview-and-setup/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/andrewsrigom/agent-skills/lucide-react-overview-and-setup"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/lucide-react-overview-and-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00092 | $0.00930 |
| Opus 5 | $0.00046 | $0.00465 |
| Sonnet 5 | $0.00018 | $0.00186 |
| Haiku 4.5 | $0.00009 | $0.00093 |
Grade A, and why
lucide-react-overview-and-setup 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 11d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lucide React Overview And Setup
Use this skill for first-time Lucide setup and for choosing the right Lucide React path before going deeper.
Scope
- installing
lucide-react - importing Lucide icons as React components
- core props like
size,color,strokeWidth, andabsoluteStrokeWidth - import naming patterns such as
House,HouseIcon, andLucideHouse - deciding when work belongs to styling and accessibility vs dynamic icons and Lucide Lab
Routing cues
- install Lucide, replace an icon library with Lucide, import icons in React, icon component props, Lucide aliases,
absoluteStrokeWidth, tree-shaking -> use this skill - global icon defaults, CSS styling,
LucideProvider, icon-only button accessibility,title,aria-label, or screen-reader behavior -> uselucide-react-styling-and-accessibility DynamicIcon, icon names from CMS or database,lucide-react/dynamic,@lucide/lab, customiconNode, or non-core icons -> uselucide-react-dynamic-icons-and-lucide-lab
Default path
- Read references/react-basics-and-setup.md first.
- Install only
lucide-reactfor standard React usage. - Prefer direct named imports from
lucide-reactso bundlers only include used icons. - Use icon props for local adjustments and route out if the task is really about app-wide defaults, accessibility, or dynamic loading.
- If the task wants icons by name or icons outside the core set, move to the dynamic and Lab skill instead of stretching base imports too far.
When to deviate
- Use import alias styles only when the codebase needs stricter naming consistency or collision avoidance.
- Reach for
@lucide/labonly when the icon is outside the core set or a custom icon node is required. - Move to dynamic loading only when icon names truly come from runtime data.
Guardrails
- Prefer direct named imports over generic dynamic loading for normal app code.
- Treat Lucide icons as React components, not raw data objects.
- Keep icon choice explicit in code when the icon set is static.
- Use the default import surface unless the task specifically needs prefixed or suffixed aliases.
absoluteStrokeWidthis for preserving stroke appearance while resizing, not a substitute for all styling decisions.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 90 lines · 92 tokens per session scan A c837aef2fdbe
lucide-react-overview-and-setup is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 92 tokens to every session and 930 once invoked, about $0.0005 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-31.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
cobejs
Use when adding a lightweight interactive globe with cobe (canvas setup, markers, interaction, performance, integration with React/Next.js).
stitch::react-components
Converts Stitch designs into modular Vite and React components, or syncs/updates existing React components to align with the latest Stitch designs, using system-level networking and AST-based validation.
seed-design
An integration guide for SEED Design, covering shared component specifications and foundations plus React and Lynx implementation guidance.
ss-studio
Turn a product brief and optional references into three distinct creative directions, a human-selected StyleSeed interaction plan, generated image/video asset jobs, a working UI prototype, and a verified prototype-first showcase reel. Use for client concepts, app interaction exploration, trendy but coherent UI…