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 agentmods add skills/db-ux-design-system/core-web/create-db-componentnpx skills add db-ux-design-system/core-web --skill create-db-componentgit clone --depth 1 https://github.com/db-ux-design-system/core-webWrote 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/db-ux-design-system/core-web/create-db-component)<a href="https://agentmods.dev/skills/db-ux-design-system/core-web/create-db-component"><img src="https://agentmods.dev/badge/skills/db-ux-design-system/core-web/create-db-component.svg" alt="Measured on agentmods" 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 | $0.00029 | $0.03681 |
| Opus 5 | $0.00015 | $0.01840 |
| Sonnet 5 | $0.00006 | $0.00736 |
| Haiku 4.5 | $0.00003 | $0.00368 |
Grade A, and why
create-db-component 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 yesterday.
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.
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.
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.
- yesterday Changed cfd7d6655fa6
- 5d ago First seen · 368 lines · 29 tokens per session scan A fe4b7b22ec40
create-db-component is a skill published in the GitHub repository db-ux-design-system/core-web (130 stars, last pushed yesterday), with no licence file. It adds 29 tokens to every session and 3,681 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-08-30.
Other skills, from other repositories
design-audit
Full project design audit that orchestrates all agents, scores across 12 dimensions, and generates a prioritized action plan. Use when the user asks to audit their design, run a design review or UX audit, review their UI, or asks how their design looks.
design-tokens
Generate or improve a complete design token system covering color, typography, spacing, radius, shadows, and motion. Use when the user asks for design tokens, to generate tokens, or to build a token system.
design-score
Quick design score card covering 12 dimensions with the top 5 improvements, in under 2 minutes. Use when the user asks for a design score, to score their design, to rate their UI, or for a quick audit.
design-compare
Compare the current design against a reference product or competitor. Use when the user asks to compare designs, run a design compare, or benchmark against another product.
frontend-design
Use this skill when specifying, designing, or documenting UI components, layouts, and design systems for frontend implementation. Trigger phrases: 'design this UI component', 'create a responsive layout', 'spec the CSS for', 'design system for'. Do NOT use for backend development, server-side logic, data engineering…
design-system
Document and define UI design system tokens, components, and guidelines.