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-dynamic-icons-and-lucide-labgit 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-dynamic-icons-and-lucide-lab)<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/lucide-react-dynamic-icons-and-lucide-lab"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/lucide-react-dynamic-icons-and-lucide-lab/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-dynamic-icons-and-lucide-lab"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/lucide-react-dynamic-icons-and-lucide-lab.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.00089 | $0.00801 |
| Opus 5 | $0.00044 | $0.00400 |
| Sonnet 5 | $0.00018 | $0.00160 |
| Haiku 4.5 | $0.00009 | $0.00080 |
Grade A, and why
lucide-react-dynamic-icons-and-lucide-lab 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 12d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lucide React Dynamic Icons And Lucide Lab
Use this skill when the app cannot rely only on static named imports from lucide-react.
Scope
DynamicIconand dynamic icon names- caveats of data-driven icon loading
@lucide/lab- the
Iconcomponent - custom
iconNodedata - choosing between direct imports, dynamic loading, and Lab/custom icons
Default path
- Read references/dynamic-and-lab.md.
- Ask whether the icon list is static or data-driven.
- If the icon set is static, route back to
lucide-react-overview-and-setupand use direct imports. - Use
DynamicIcononly when icon names truly come from runtime data such as CMS entries or database rows. - Use
Iconwith@lucide/labor custom icon nodes when the app needs icons outside the core Lucide package.
When to deviate
- Keep the core package only when all icons are in the main Lucide set.
- Use
Iconplus@lucide/labfor non-core or custom nodes rather than forcing everything throughDynamicIcon. - Validate or normalize icon names before render when they come from remote data.
- Move back to the overview skill when the icon set turns out to be static after all.
Guardrails
DynamicIconis not the default path; it increases build and delivery cost.- Expect SSR and loading-state considerations when icon names are resolved dynamically.
- Keep runtime icon names validated or normalized instead of trusting arbitrary strings.
- Use
Iconfor Lucide Lab or custom icon nodes, notDynamicIcon. - Treat
@lucide/labas an extension set, not the baseline icon dependency for every project.
Avoid
- using
DynamicIconfor a static set of known icons - trusting arbitrary runtime icon names without validation
- treating
@lucide/labas a required dependency for normal app usage - using
DynamicIconwhen the real need is a Lab or custom icon node
Verification checklist
- the icon set is confirmed to be static or runtime-driven
DynamicIconis only used for real runtime-name scenarios- Lab or custom nodes use
Icon, notDynamicIcon - remote icon names are validated or normalized
- SSR and loading behavior are considered when icons load dynamically
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.
- 12d ago First seen · 89 lines · 89 tokens per session scan A 2710797c9e6f
lucide-react-dynamic-icons-and-lucide-lab is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 89 tokens to every session and 801 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-31.
Other skills, from other repositories
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
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…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
fuzzy-ranking
Rank fuzzy matches with rankItem, filter with RankingInfo.passed, compare saved ranking metadata with compareItems, and configure rankings, thresholds, accessors, min/max bounds, or diacritics. Load for @tanstack/match-sorter-utils itself or fuzzy Table filterMeta wiring.
api-not-found
Diagnose missing TanStack Table v9 exports, options, state slices, and instance methods. Load before inventing an API when code sees a type error, undefined feature method, absent object key, adapter mismatch, or v8-shaped example.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.