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/sgaabdu4/hard-eng/atomic-uinpx skills add sgaabdu4/hard-eng --skill atomic-uigit clone --depth 1 https://github.com/sgaabdu4/hard-engWrote 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/sgaabdu4/hard-eng/atomic-ui)<a href="https://agentmods.dev/skills/sgaabdu4/hard-eng/atomic-ui"><img src="https://agentmods.dev/badge/skills/sgaabdu4/hard-eng/atomic-ui.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.1 | $0.00031 | $0.00537 |
| Opus 5 | $0.00015 | $0.00269 |
| Sonnet 5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
atomic-ui 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atomic UI
Contract
- Input = accepted UI behavior + current design/style/component owners.
- Repository visual SSOT = root
DESIGN.md+ production token/theme/component owners. - Visual SSOT = tokens/theme + primitives + composed components + layout/page owners; hierarchy ≠ folder dogma.
- Reusable visual/interaction decision → canonical owner; true one-off constraint may remain local.
- Component earns ownership through behavior, styling, or composition; pass-through component = reject.
- New material product/UX direction →
he; this skill preserves accepted design during implementation/review. - Direct local UI edit = existing production owner + focused proof; context-doc debt alone never blocks/escalates.
Route
| Need | Action |
|---|---|
Missing/invalid/stale DESIGN.md + direct local UI edit |
Reuse closest production owner; report context debt only if relevant |
Missing/invalid/stale DESIGN.md + eligible lifecycle/design-system work |
Load design-md.md |
| Existing SSOT + local UI edit | Reuse closest token/primitive/component/layout owner |
Valid DESIGN.md + missing/duplicate production owners |
Load system.md |
| React/Next implementation | Also vercel-react-best-practices |
| Flutter + Riverpod implementation | Also building-flutter-apps |
| Other Flutter implementation | Existing project design/style owners only |
| Real browser/device proof | e2e |
Ownership
he-plan= desired flows/UX/prototype decision.atomic-ui= production token/component/layout ownership evidence.- Stack skill = framework mechanics;
deterministic-checks= commands/scanners/gates.
Complete
- Direct local edit = requested behavior + closest production owner + focused visual/a11y proof.
- Existing UI prototype = real before screen + closest production component/layout owner + preserved current anchors + accepted-flow comparison.
- Lifecycle/design-system edit = root
DESIGN.mdvalid/current + token/theme/component owner named. - Reuse/new-owner evidence explicit.
- Loading/empty/error/permission/disabled/focus/hover states covered as applicable.
- Responsive + semantic role/name/state + keyboard/focus + contrast/reflow/motion/touch behavior proven or exact gap reported.
- No duplicated reusable visual value or owner remains in touched blast radius.
What ships with it
3 files 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.
- 6d ago First seen · 46 lines · 31 tokens per session scan A e9b823dc9210
atomic-ui is a skill published in the GitHub repository sgaabdu4/hard-eng (5 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 537 once invoked, about $0.0002 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
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…
ui-first-builder
Creates production-ready UI immediately from any description. Generates complete pages, components, and realistic mock data in FIRST response. Uses Next.js 16 + Tailwind + shadcn/ui. Never asks questions - infers everything from context. Triggers: UI creation, page building, component generation, build interface…
kirby-performance-and-media
Improves Kirby performance and media delivery (cache tuning, CDN, responsive images, lazy loading). Use when optimizing page speed, caching, or image handling.
landing-page-generator
Generates high-converting Next.js/React landing pages with Tailwind CSS. Uses PAS, AIDA, and BAB frameworks for optimized copy/components (Heroes, Features, Pricing). Focuses on Core Web Vitals/SEO.