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/skill-library/kanzen/v1/boring-triage/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-triage)<a href="https://agentmods.dev/skills/hachej/boring-ui/boring-triage"><img src="https://agentmods.dev/badge/skills/hachej/boring-ui/boring-triage.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.01249 |
| Opus 5 | $0.00026 | $0.00624 |
| Sonnet 5 | $0.00010 | $0.00250 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
boring-triage 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 8d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boring Triage
Triage answers: what is the first unmet gate, then does one next action.
Sweep
- Refresh issue/PR body, comments, current labels, CI, reviews, proof comment, and head SHA.
- Read newest Julien/owner instruction before touching the item.
- Read enough code/docs to know risk and proof path.
- Pick queued or stale work, then stop at the first unmet gate.
- Record labels, gate, proof, reviewed SHA, and next action.
Labels
| Kind | Rule | Values |
|---|---|---|
state:* |
exactly one | queued, blocked, active, ready, done |
phase:* |
exactly one | triage, grill, plan, implement, review, merge |
track:* |
exactly one | owner by default, fast only after risk gate |
| source | optional | source:feedback only |
- No taxonomy labels:
bug,ui,accessibility,package:*,plugin:*,gate:*. - Put details in body/card.
Gate Table
| Situation | Labels | Gate |
|---|---|---|
| weak issue body or unsafe intake | state:queued phase:triage |
intake |
| queued issue is ready to classify | state:queued phase:triage |
triage |
| duplicate, invalid, out of scope | state:done |
none |
| unclear | state:blocked phase:grill |
clarity |
| risk classification | keep track:owner; upgrade to track:fast only if eligible |
risk |
| runtime exposure is not controlled | keep current state/phase | flag |
| needs design or sequencing | state:active phase:plan |
plan |
| clear and no PR | state:active phase:implement |
implementation |
| PR lacks current review, has unresolved comments, or accepted findings remain | state:active phase:review |
implementation |
| final proof comment, tests, CI, or demo proof missing | state:active phase:review |
proof |
| all gates pass | state:ready phase:merge |
merge |
Gate Actions
| Gate | Action |
|---|---|
intake |
repair the issue using docs/kanzen/procedures/well-documented-issue.md |
clarity |
use boring-loop-grill: grill-me plus ask-user; stay state:blocked phase:grill |
triage |
classify risk, plan need, implementation state, proof, and merge readiness |
risk |
keep track:owner; upgrade to track:fast only when all fast-track rules pass |
flag |
require not-needed, a safe feature flag, or an abstraction path before code proceeds |
plan |
use boring-loop-plan: smallest useful plan; plan file plus thermo review for risky or multi-PR work |
implementation |
use boring-loop-implement: one accountable lane for one issue/PR |
proof |
follow docs/kanzen/procedures/proof-of-work.md; PR body proof is not a substitute for the final proof comment |
merge |
fast-track merge or docs/kanzen/procedures/owner-review-card.md |
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.
- 8d ago First seen · 113 lines · 52 tokens per session scan A 980a772a51b6
boring-triage is a skill published in the GitHub repository hachej/boring-ui (46 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 1,249 once invoked, about $0.0003 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.
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…