Borrowing it
Nothing to install: this file belongs to hachej/boring-ui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hachej/boring-ui/main/.agents/skills/boring-plugin-build/SKILL.mdgit 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/boring-plugin-build)<a href="https://agentmods.dev/skills/hachej/boring-ui/boring-plugin-build"><img src="https://agentmods.dev/badge/skills/hachej/boring-ui/boring-plugin-build.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.00071 | $0.02235 |
| Opus 5 | $0.00036 | $0.01118 |
| Sonnet 5 | $0.00014 | $0.00447 |
| Haiku 4.5 | $0.00007 | $0.00224 |
Grade A, and why
boring-plugin-build 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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boring Plugin Build
Companion files in this skill bundle
Read these companion docs when needed:
DECISION_TREE.md— choose the plugin shape firstREGISTRATION_MATRIX.md— map plugin surfaces to the right load pathPROGRESS_DISCLOSURE.md— how to report plugin progress clearlyCHECKLISTS.md— shape, registration, and verification checklistsSNIPPETS.md— copy-paste commands for runtime plugins, app plugins, core boot, and Vercel entry wiring
The one rule
Decide plugin trust level before you write files.
There are two valid plugin shapes in this repo:
- runtime/generated plugin under
.pi/extensions/<name>/ - app/internal trusted plugin package declared through
package.json#boring.defaultPluginPackages
If the plugin is part of a real shipped app, default to app/internal trusted package. If the plugin is for fast local iteration or agent-authored experimentation, default to runtime/generated plugin.
Read these first
packages/pi/skills/boring-plugin-authoring/SKILL.mdpackages/workspace/docs/PLUGIN_STRUCTURE.mdpackages/workspace/docs/PLUGIN_SYSTEM.mdpackages/core/docs/PLUGIN_INTEGRATION.mdwhen the plugin is for a core-based shipped appapps/workspace-playground/README.mdapps/workspace-playground/src/front/App.tsxapps/workspace-playground/package.jsonapps/workspace-playground/src/plugins/playgroundDataCatalog/package.json
Treat packages/pi/skills/boring-plugin-authoring/SKILL.md as the deep canonical authoring manual. This local skill is the repo-specific dispatcher that tells you which path to use.
Also follow PROGRESS_DISCLOSURE.md while implementing so the user always knows the current plugin shape, load path, and restart/reload requirement.
Use DECISION_TREE.md before writing files.
Decision table
| Need | Choose |
|---|---|
live local experimentation, /reload, no trusted backend routes |
.pi/extensions/<name>/ |
| app-owned domain logic, trusted routes/tools, production app package | app/internal plugin package |
| provider/binding plugin that wraps React tree | app/internal plugin package + static front composition |
| panel/command/catalog/surface-resolver only | either, but shipped apps usually use app/internal packages |
What ships with it
5 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.
- 3d ago First seen · 293 lines · 71 tokens per session scan A 31991375df95
boring-plugin-build is a skill published in the GitHub repository hachej/boring-ui (46 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 2,235 once invoked, about $0.0004 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-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…