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 blockmatic/basilic --skill use-frontendgit clone --depth 1 https://github.com/blockmatic/basilicWrote 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/blockmatic/basilic/use-frontend)<a href="https://agentmods.dev/skills/blockmatic/basilic/use-frontend"><img src="https://agentmods.dev/badge/skills/blockmatic/basilic/use-frontend.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.00653 |
| Opus 5 | $0.00016 | $0.00327 |
| Sonnet 5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
use-frontend 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 2d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose and inputs
Build or reshape a user-facing surface. Planning a feature without UI work stays on /plan-feature. Installing a primitive stays on /use-shadcn. Do not write PRODUCT.md or DESIGN.md. Do not install animation libraries or design-detector hooks.
Load frontend-design-v1 for visual direction, composition-patterns-v1 for reusable APIs, and web-design-guidelines-v1 for the UI code checklist. Product jobs belong to /f-journeys when the change is durable.
Steps
- Purpose and audience. Name the job, the person, and the surface mode: Operate (app/task), Persuade (marketing), or Read (docs). Durable jobs stay in the Journeys overlay; do not generate DESIGN.md.
- Visual references. Use the brief, existing screens, or a stated aesthetic. If the repo has tokens and shared components, inspect those first. Tokens win over a greenfield palette (
frontend-design-v1/references/product-ui.md). - Reuse before invent. Prefer shared primitives. Compose at the second call site. Do not extract a compound API for a one-off route. Do not lift server data into a client provider.
- Responsive and interaction. Mobile-first layout, visible focus, keyboard path,
prefers-reduced-motion. Do not add a new motion library. - Harden states. Loading, empty, error, success, and long/overflow content. Skip a full i18n/RTL program unless the repo already localizes.
- Implement the smallest slice that completes the job.
- Rendered verification (bounded). Inspect desktop and mobile together. Exercise primary interactions and keyboard navigation. Critique screenshots. Fix evidenced issues in one batch. Confirm with at most one more pass, then stop. If browser tools are missing, say so and use the closest substitute. A type check is not visual QA.
- Optional checklists.
/audit-accessibilityfor the Quality overlay (do not invent a WCAG level).@web-design-guidelines-v1for code-level interface rules. Playwright E2E only when an existing spec covers the path—it does not replace the screenshot loop.
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.
- 2d ago First seen · 36 lines · 32 tokens per session scan A 5c0c94c40e6c
use-frontend is a skill published in the GitHub repository blockmatic/basilic (89 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 653 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-09-06.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
reveal-hover-effect
Build cursor-following spotlight reveals that expose a second aligned image through a soft radial mask. Use for hover-to-color, before-and-after, x-ray, material, texture, product-detail, and illustrated hero effects where a desaturated or embossed base image should remain visible while another treatment follows an…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
better-colors
Helps you build a color system and answer anything about color in your project. You can generate palettes, use semantic tokens, convert between formats, check contrast and more.