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 hachej/boring-ui --skill add-blocksgit clone --depth 1 https://github.com/hachej/boring-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/hachej/boring-ui/add-blocks)<a href="https://agentmods.dev/skills/hachej/boring-ui/add-blocks"><img src="https://agentmods.dev/badge/skills/hachej/boring-ui/add-blocks/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/hachej/boring-ui/add-blocks"><img src="https://agentmods.dev/badge/skills/hachej/boring-ui/add-blocks.svg" alt="Reviewed on agentmods" width="80" 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.00136 | $0.02203 |
| Opus 5.5 | $0.00054 | $0.00881 |
| Sonnet 5.5 | $0.00027 | $0.00441 |
| Haiku 4.5 | $0.00014 | $0.00220 |
Grade A, and why
add-blocks 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 3d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add and maintain blocks
Blocks are shadcn registry items: React source the shadcn CLI copies into the app. They are generated copies. The app installs them, configures them through props and theme tokens, and updates them with one command. It never edits them.
Prerequisites: React 19, Tailwind v4, a components.json with a Base UI style (only base-nova is supported), and @hachej/boring-ui-kit installed (the boring-ui-blocks command is its bin). A new app starts with npx [email protected] init -t vite -b base -p nova -n app -y --no-monorepo.
Blocks import the app's shadcn components through its ui alias (components.json) and use its tokens; no block lists them. Install them once, before any block (what the app needs):
npx boring-ui-blocks add alert attachment avatar badge bubble button card checkbox collapsible dialog drawer dropdown-menu empty input input-group item label message message-scroller native-select popover progress scroll-area separator sidebar spinner switch table textarea toggle toggle-group tooltip trace
Run every command in the directory that holds components.json, or pass --cwd <dir>.
Find a block
The registry for version <v> is https://cdn.jsdelivr.net/npm/@hachej/boring-ui-kit@<v>/r/. The installed kit ships the same items in node_modules/@hachej/boring-ui-kit/r/. List them with their descriptions:
node -e "const r=JSON.parse(require('fs').readFileSync('node_modules/@hachej/boring-ui-kit/r/registry.json','utf8'));for(const i of r.items)console.log(i.name.padEnd(18),(i.description??'').slice(0,90))"
Pick by placement (full table):
| Need | Block |
|---|---|
| The conversation only, in your own layout | pi-chat |
| A floating bar over an existing site | pi-ambient (brings pi-chat, pi-workspace) |
| Chat plus a resizable artifact panel | pi-workspace (brings pi-chat) |
| A whole agent page: sessions, chat, viewers | pi-app (brings pi-chat, pi-workspace, viewers) |
| One agent above any app, drawer on phones | app-shell (brings pi-chat, feedback, sidebar, avatar, drawer, dropdown-menu) |
| Chat and files in resizable docks | dock |
| The Library and file history alone | file-tree, documents, version-history |
| Viewers for agent artifacts | viewers, markdown-editor, html-viewer, mockup-viewer, diagram-viewer, maquette-viewer, record-viewer, board-viewer, task-list-viewer |
| User feedback (point, dictate, send) | feedback, feedback-preview |
| Model and key picker | provider-setup |
| Floating utility windows | windows |
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.
- 3d ago Changed d91260da8235
- 4d ago Changed · +6 lines e53bf5493c40
- 5d ago Changed · +2 lines b7cd8e5a1afa
- 9d ago First seen · 116 lines · 136 tokens per session scan A 4a74cf815e40
add-blocks is a skill published in the GitHub repository hachej/boring-ui (49 stars, last pushed today), licensed MIT. It adds 136 tokens to every session and 2,203 once invoked, about $0.0005 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-10-23.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.