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 instructions/pedrobalsa/balsa-ui/agents-mdgit clone --depth 1 https://github.com/pedrobalsa/balsa-uiWhat 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.00156 | $0.00156 |
| Opus 5 | $0.00078 | $0.00078 |
| Sonnet 5 | $0.00031 | $0.00031 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
balsa-ui AGENTS.md 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.
What it actually says
Balsa UI contributor guide
- Start with
.balsa/catalog-index.json, then read the selectedspecs/components/<name>.jsonand canonical source. - Edit canonical files under
src/; never directly edit generatedregistry/vue,public/r, starter component/style copies, or smoke-fixture component/style copies. - Use Vue 3
<script setup lang="ts">, strict typed APIs, semantic Balsa tokens, existing primitives, and accessible native behavior. - Keep source, specification, registry metadata, Markdown documentation, focused tests, and changelog aligned.
- Preserve local changes and inspect
git diffbefore handoff. - Run
npm run check:changedfor ordinary work andnpm run checkfor release or distribution integration.
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 · 9 lines · 156 tokens per session scan A 9ae55999e18a
balsa-ui AGENTS.md is an instructions file published in the GitHub repository pedrobalsa/balsa-ui (49 stars, last pushed 13d ago), licensed MIT. It adds 156 tokens to every session, about $0.0008 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 instructions, from other repositories
ui-components AGENTS.md
Instructions for starc007/ui-components, covering beui v2 — agent guide, commands, layout, component catalog and components (motion category — primitives).
ui-components CLAUDE.md
Instructions for starc007/ui-components, a project described as: Motion components for React. Copy, paste, done.
magicui AGENTS.md
Instructions for magicuidesign/magicui, covering project context, key principles, before writing code, rules and accessibility (a11y).
supermemory CLAUDE.md
Instructions for supermemoryai/supermemory, covering claude.md, repository structure, applications (apps/), development commands and root level (monorepo).
ui AGENTS.md
Instructions for nuxt/ui, covering agents.md, project overview, project structure, commands and cli for scaffolding.
ark CLAUDE.md
Instructions for chakra-ui/ark, covering ark ui - claude development guide, documentation structure, quick start, common commands and install dependencies.