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 pedrobalsa/balsa-ui --skill balsa-template-designgit clone --depth 1 https://github.com/pedrobalsa/balsa-uiWrote 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/pedrobalsa/balsa-ui/balsa-template-design)<a href="https://agentmods.dev/skills/pedrobalsa/balsa-ui/balsa-template-design"><img src="https://agentmods.dev/badge/skills/pedrobalsa/balsa-ui/balsa-template-design/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/pedrobalsa/balsa-ui/balsa-template-design"><img src="https://agentmods.dev/badge/skills/pedrobalsa/balsa-ui/balsa-template-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 89 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00088 | $0.01167 |
| Opus 5.5 | $0.00035 | $0.00467 |
| Sonnet 5.5 | $0.00018 | $0.00233 |
| Haiku 4.5 | $0.00009 | $0.00117 |
Grade A, and why
balsa-template-design 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Distinctive Balsa Templates
Use this skill with $balsa-ui. This skill owns art direction and composition; $balsa-ui
owns discovery, exact component contracts, installation, accessibility, source placement, and
validation. Keep the implementation in Vue 3 <script setup lang="ts"> and preserve the
active Balsa design system.
Ground the template in a subject
- Choose one concrete subject, audience, and primary job when the brief leaves them open.
- Build with realistic names, labels, values, states, and domain language. Keep demo content specific even when the template API remains reusable.
- Derive visual character from the subject's real materials, tools, artifacts, environment, and vernacular. Do not substitute generic SaaS copy or invented vanity metrics.
Art-direct before coding
Create a compact internal plan before editing:
- Thesis — state the visual idea in one sentence.
- Container model — choose the page structure: open canvas, bands, rails, list, table, master-detail, editorial columns, media frame, deliberate Card system, or another model justified by the content.
- Typography — assign title, body, control, label, and data roles. Use the active theme's roles unless the brief explicitly calls for an authored design system.
- Palette and material — map hierarchy to Balsa semantic tokens and theme-owned surfaces. Reserve product-specific color for decoration that need not adapt with the palette.
- Density and rhythm — choose controlled density or generous space and repeat a small spacing rhythm consistently.
- Signature — choose one memorable, subject-specific compositional move.
- Restraint — name what stays quiet so the signature remains legible.
Use an ASCII wireframe when the hierarchy or container model is not obvious from the brief. If an attached reference or generated concept is the visual specification, extract this plan from it and preserve its hierarchy, density, geometry, and media treatment.
What ships with it
2 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.
- 1mo ago First seen · 106 lines · 88 tokens per session scan A fb204f5c3eb8
balsa-template-design is a skill published in the GitHub repository pedrobalsa/balsa-ui (63 stars, last pushed 2mo ago), licensed MIT. It adds 88 tokens to every session and 1,167 once invoked, about $0.0004 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-30.
Other skills, from other repositories
nuxt-ui
Build UIs with @nuxt/ui v4 — 125+ accessible Vue components with Tailwind CSS theming. Use when creating interfaces, customizing themes to match a brand, building forms, or composing layouts like dashboards, docs sites, and chat interfaces.
frappe-ui
Build consistent Frappe-style user interfaces using the frappe-ui Vue 3 component library and its design tokens. Use when scaffolding pages, forms, dialogs, lists, or any UI inside a Frappe-based app, when the user mentions frappe-ui, Frappe Cloud / Gameplan / Desk / Drive / Insights styling, or asks to "use frappe-ui…
ui-components
UI component library patterns for shadcn/ui and Radix Primitives. Use when building accessible component libraries, customizing shadcn components, using Radix unstyled primitives, or creating design system foundations.
ban-pattern
A design-system rule for recording interface patterns that should not be used because they make a UI look generic or AI-generated.
build-screen
A step-by-step procedure for building one interface screen from a project's existing design contracts. It asks a small number of clarifying questions, creates the screen, and reports what it checked.
design-review
A review procedure for checking an HTML file against the melta UI design system, which is a set of rules for how an interface should look and behave.