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 skills/hachej/boring-ui/plannpx skills add hachej/boring-ui --skill plangit 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/plan)<a href="https://agentmods.dev/skills/hachej/boring-ui/plan"><img src="https://agentmods.dev/badge/skills/hachej/boring-ui/plan.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 | $0.00025 | $0.00652 |
| Opus 5 | $0.00013 | $0.00326 |
| Sonnet 5 | $0.00005 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
plan 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 4d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan
Plan before coding. This is a planning loop: produce the first useful spec/plan, run adversarial review when risk is non-trivial, revise once for accepted findings, and exit with a clear state. This is to-spec first; use to-tickets behavior only when the work is too large for one safe implementation slice.
Modes
- Spec mode: clarify what should be built.
- Slice mode: split the spec into tracer-bullet vertical slices with blocking edges.
Process
- Read
docs/kanzen/MODEL-CARD.mdfor reviewer/escalation policy when available. - Read the source issue/spec/conversation, comments, related PRs, existing plan files, and relevant code/docs.
- Produce or update a spec/plan. Prefer issue comments for small work; use
docs/issues/<issue>/plan.mdfor risky, broad, or multi-slice work. - Identify test seams and proof before implementation starts.
- If the work is broad, split into vertical slices. Each slice must be demoable/verifiable alone.
- For wide mechanical refactors, do not force fake vertical slices; use expand → migrate batches → contract.
- Run an adversarial plan review when triggered by the model card: challenge scope, flag path, blockers, proof, review budget, and whether the plan is too broad.
- Revise for accepted findings.
- Mark the next action:
ready-for-agent,ready-for-human, orneeds-info. - If the next action requires human input, use the
ask_usertool when available so the request appears in the Boring UI inbox. If unavailable, leave a GitHub issue comment.
Plan Shape
## Problem Statement
## Solution
## User Stories / Scenarios
## Decisions
## Flag / Abstraction
- Needed?:
- Path:
- Rollback:
## Test Seams
- Highest public seam:
- Existing prior art:
- Avoid testing:
## Acceptance
## Proof
- Exact command:
- Screenshot/demo:
- Manual steps:
- Waiver if proof is not possible:
## Slices
### Slice: <name>
**Delivers:**
**Blocked by:** None / <slice or issue>
**Proof:** exact command, screenshot/demo, manual steps, or waiver
**Review budget:** inside / exceeds / why
## Wide Refactor Strategy
Expand → migrate batches → contract, if applicable.
## Out of Scope
## Open Questions
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.
- 4d ago First seen · 83 lines · 25 tokens per session scan A 485743651c9c
plan is a skill published in the GitHub repository hachej/boring-ui (46 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 652 once invoked, about $0.0001 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…