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 refsgit 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/refs)<a href="https://agentmods.dev/skills/dkadts/landing-kit-building/refs"><img src="https://agentmods.dev/badge/skills/dkadts/landing-kit-building/refs/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/refs"><img src="https://agentmods.dev/badge/skills/dkadts/landing-kit-building/refs.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.00058 | $0.01760 |
| Opus 5.5 | $0.00023 | $0.00704 |
| Sonnet 5.5 | $0.00012 | $0.00352 |
| Haiku 4.5 | $0.00006 | $0.00176 |
Grade A, and why
refs 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 1mo 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/refs
Reads every folder under references/*/, extracts patterns per aspect, surfaces conflicts, and produces two artifacts:
references/proposal.md— recommendations for/design-lock.references/approved-manifest.md— a flat list of required elements the user approved (see Step 5b).
When to use
- After
brief/05-design.mdis filled. - The user placed references in
references/. - Before
/design-lock.
Requirements
- At least 1 reference exists somewhere under
references/*/. brief/05-design.mdis filled (mood, associations).
If no references at all — offer to base the design on brief/05-design.md and skip this skill.
Process
Step 1. Walk every aspect folder.
For each folder in references/:
animation/,structure/,typography/,color/,layout/,motion/,micro-interactions/,mood/,full-sites/- Read every subfolder:
source.txt,notes.md, media files. - If the user provided a URL but no screenshot, WebFetch the visual/structure (do not pull code).
Step 2. Extract the common pattern per aspect.
For each aspect, articulate what's shared across references:
## animation
From 3 references:
- Common pattern: subtle scale-up on hover (1.02×), fade + slight lift on scroll
- Common ease: cubic-bezier(0.22, 1, 0.36, 1)
- Common duration: ~300ms
- Outlier: <linear-refs uses longer 500ms>
## typography
- Serif heading + sans body (2 of 3)
- Ratio ~1.333 (Perfect Fourth)
- Weights: 400 body, 700 headings — only two
- Heading line-height: 1.1 (tight, editorial)
Step 3. Detect conflicts.
Run through the pairs:
- Mood vs Motion: "quiet luxury" + "bombastic scroll animations" → conflict.
- Color vs Mood: "warm beige" + "neon accent" → conflict (unless neon is a declared subversion).
- Density vs Typography: "compact" + "editorial serif big display" → conflict.
- Density vs Structure: "editorial density" + "5+ sections" → conflict (editorial = fewer sections, more air).
Each conflict is a question to the user:
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.
- 1mo ago First seen · 170 lines · 58 tokens per session scan A 946a49b8156a
refs is a skill published in the GitHub repository dkadts/landing-kit-building (2 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 1,760 once invoked, about $0.0002 per session on Opus 5.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.
anti-slop-design
Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.
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…
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".
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).…
write-mermaid-diagram
Mermaid authoring and rendering mechanics across every diagram type - picking the type from the question the reader is asking, the label and escaping rules that decide whether a diagram parses, rendering .mmd to SVG or PNG with the mermaid CLI, proving a render actually succeeded, and which surfaces render Mermaid at…