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 dkadts/landing-kit-building --skill iconsgit clone --depth 1 https://github.com/dkadts/landing-kit-buildingWrote 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/dkadts/landing-kit-building/icons)<a href="https://agentmods.dev/skills/dkadts/landing-kit-building/icons"><img src="https://agentmods.dev/badge/skills/dkadts/landing-kit-building/icons/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/dkadts/landing-kit-building/icons"><img src="https://agentmods.dev/badge/skills/dkadts/landing-kit-building/icons.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.00064 | $0.02271 |
| Opus 5 | $0.00032 | $0.01136 |
| Sonnet 5 | $0.00013 | $0.00454 |
| Haiku 4.5 | $0.00006 | $0.00227 |
Grade A, and why
icons 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/icons
Icons are a common failure point: mixed libraries, mismatched stroke weights, decorative-only icons, hallucinated SVG shapes. This skill enforces one library, one style, verified geometry.
When to use
- After
/media— media assets are in place, now icons are the last visual asset. - Before
/build— build references the icon set fromsite/media/icons/. - Rerun anytime a new concept is added to the copy.
Requirements
DESIGN-LOCK.mdLOCKED (need §2 type, §3 color, §5 motion, §7 imagery for style spec).brief/copy-analysis.mdexists (concepts are extracted from here).inbox/texts/populated (backup source for concept extraction).
Process
Step 1. Extract concepts from context
Read:
brief/01-business.md— niche, product, services.brief/copy-analysis.md— recommended section structure and key claims.brief/03-goals.md— CTA labels and offer names.inbox/texts/*— surface-level scan for repeating nouns.
Extract 5-15 icon concepts. Each concept is a short label + intent:
- consulting → conversation, expertise
- roadmap → path, planning
- reporting → chart, transparency
- fast-turnaround → clock, speed
- privacy → lock, safety
- multi-region → globe, coverage
Present the extracted list to the user. Ask: "add, remove, or rename any concepts before we map to icons?"
Step 2. Compute style spec from DESIGN-LOCK
Read DESIGN-LOCK and derive:
Style spec
stroke-width: <derived from type §2 body-weight and radius §4>
thin (1px) if radius = 0
regular (1.5px) if radius ≤ 8
bold (2px) if radius ≥ 12 or pill
corner-style: sharp if radius = 0 else rounded
fill-style: outline (default) | filled (only if brand uses heavy typography)
| duotone (only if palette §3 is duotone/tritone)
size-baseline: 24×24 viewBox
color-strategy: currentColor (inherit from text via CSS)
geometric-complexity: minimal (≤ 2 paths) | detailed (up to 4 paths)
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 · 211 lines · 64 tokens per session scan A fec15df7143a
icons is a skill published in the GitHub repository dkadts/landing-kit-building (2 stars, last pushed 21d ago), licensed MIT. It adds 64 tokens to every session and 2,271 once invoked, about $0.0003 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
frontend-design
Visual and UX design quality for interfaces: hierarchy, spacing rhythm, typographic scale, a restrained color system, layout composition, and polished states. The taste layer above frontend architecture and a11y.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for…
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…
options
Present multiple design options as a vertical stack of anchored turns.
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.