core-components

core-components is a skill for Claude Code, Codex from Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI. It costs 27 tokens per session (296 once invoked), scanned A, original, no licence file.

A reference for reusable interface components and design-system patterns, including shared design tokens.

In plain words
What is it for?
It supports building interfaces, applying design tokens, and working with shared UI components.
Why use it?
It helps keep user interfaces consistent when building or extending a component library.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

Good fit It supports building interfaces, applying design tokens, and working with shared UI components.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dokhacgiakhoa/agent-skills-4-vibe-coding-cli/core-components
Install

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.

Any agent
npx skills add Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill core-components
Clone the repo
git clone --depth 1 https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for core-components

README.md
[![agentmods](https://agentmods.dev/badge/skills/dokhacgiakhoa/agent-skills-4-vibe-coding-cli/core-components/github.svg)](https://agentmods.dev/skills/dokhacgiakhoa/agent-skills-4-vibe-coding-cli/core-components)
Your own site
<a href="https://agentmods.dev/skills/dokhacgiakhoa/agent-skills-4-vibe-coding-cli/core-components"><img src="https://agentmods.dev/badge/skills/dokhacgiakhoa/agent-skills-4-vibe-coding-cli/core-components/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.

agentmods 80×15 button for core-components

Your own site · 80×15
<a href="https://agentmods.dev/skills/dokhacgiakhoa/agent-skills-4-vibe-coding-cli/core-components"><img src="https://agentmods.dev/badge/skills/dokhacgiakhoa/agent-skills-4-vibe-coding-cli/core-components.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 296 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.00296
Opus 5 $0.00014 $0.00148
Sonnet 5 $0.00005 $0.00059
Haiku 4.5 $0.00003 $0.00030

Measured 6d ago against content hash 07a91bccb3fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

core-components 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 6d 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.

.agent/skills/core-components/SKILL.md · 31 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

Changes

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.

  1. 6d ago First seen · 31 lines · 27 tokens per session scan A 07a91bccb3fc

Subscribe to this mod's changes

core-components is a skill published in the GitHub repository Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI (508 stars, last pushed 3mo ago), with no licence file. It adds 27 tokens to every session and 296 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-09-03.

Related

Other skills, from other repositories

frontend-taste

Premium frontend design skills that override LLM defaults. Prevents generic 'AI-looking' UI. Enforces deterministic typography, calibrated color, asymmetric layouts, spring physics, hardware-accelerated motion. Triggers: 'UI tasarla', 'design a UI', 'premium landing page', 'frontend taste', 'anti-slop', 'dashboard…

fatihkan/badi · 0 tokens

design-tokens

Project-level DESIGN.md tokens reference. When the project has a DESIGN.md file, agents producing UI / components / visuals must consult this skill to use canonical color/typography/spacing tokens rather than inventing new ones. Triggers on: UI generation, component creation, design brief, visual asset, tailwind…

fatihkan/badi · 0 tokens

ui-audit

Audit UI for design token compliance and component adoption. Static grep-based analysis against the sitemap's page and component files. Requires a design system with semantic tokens.

marcoguillermaz/Tierward · 35 tokens

interaction-physics

Design and implement the motion layer of a UI — microinteractions, transitions, hover/press feedback, and animation timing/easing — as working CSS/JS plus a written animation spec. Use when the user says 'the app feels janky', 'animations feel off', 'make it feel smoother/snappier', 'add a transition', 'the modal just…

sanky369/vibe-building-skills · 138 tokens

design-foundation

Create or extract a design-token foundation — colors, typography, spacing, radii, shadows — as a real tokens file (CSS variables and/or Tailwind theme) plus a migration map from current hardcoded values. Use when the user says 'set up a design system', 'our styles are inconsistent', 'we have 50 shades of the same…

sanky369/vibe-building-skills · 151 tokens

typography-system

Build or repair a typography system: a modular type scale, font choices and loading, hierarchy, line-height/line-length, and fluid sizing — delivered as tokens (Tailwind fontSize config or CSS variables) applied to real components. Use when the user says 'the text looks off', 'fonts are inconsistent', 'headings don't…

sanky369/vibe-building-skills · 137 tokens