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-orchestration/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-orchestration)<a href="https://agentmods.dev/skills/hachej/boring-ui/boring-orchestration"><img src="https://agentmods.dev/badge/skills/hachej/boring-ui/boring-orchestration.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.00035 | $0.00589 |
| Opus 5 | $0.00017 | $0.00295 |
| Sonnet 5 | $0.00007 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
boring-orchestration 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boring Orchestration
Run scheduled /triage.
Canonical model: ../../../../../docs/kanzen/boring-loop.md.
How-to details: ../../../../../docs/kanzen/procedures/.
Sweep
- Refresh issues, PRs, comments, labels, CI, reviews, proof, head SHA, sessions.
- Read newest owner instruction.
- Run
boring-triage. - Execute first unmet gate only.
- Record labels, gate, proof/reviewed SHA, next action, sessions.
Gates
| Gate | Action |
|---|---|
intake |
repair issue body: context, redaction note, first plan |
triage |
run boring-triage; classify first real gate |
clarity |
use boring-loop-grill; grill-me plus ask-user when async |
risk |
keep track:owner; upgrade only when fast-track rules pass |
flag |
require not-needed, safe feature flag, or abstraction path |
plan |
use boring-loop-plan; issue-linked plan for risky or multi-PR work |
implementation |
use boring-loop-implement; one parent lane owns one issue/PR |
proof |
tests, CI, proof-of-work comment, screenshots, and demo proof when useful |
merge |
fast-track merge if all gates pass, otherwise owner review |
Rules
- Labels: only
state:*,phase:*,track:*, optionalsource:feedback. - Sessions: comments only; include id, purpose, scope, reason.
- Lane: one parent thread/run, one checkout context, one GitHub item.
- Subagents: allowed for slices/review; return findings to parent lane.
- Trunk/budget:
../../../../../docs/kanzen/procedures/trunk-flags-review-budget.md. - Issue plans:
../../../../../docs/kanzen/procedures/issue-plans.md. - Proof:
../../../../../docs/kanzen/procedures/proof-of-work.md. - Commit/coding rules:
../../../../../docs/kanzen/procedures/coding-rules.md. - Review: fix/re-review plus thermo until clean or blocked.
- Head SHA: proof, review, thermo must match.
- Owner review: use
../../../../../docs/kanzen/procedures/visual-review.md.
Merge
- Apply fast-track checklist in
../../../../../docs/kanzen/boring-loop.md. - If any item fails: owner review brief,
track:owner.
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 · 53 lines · 35 tokens per session scan A 77bbd33802fc
boring-orchestration is a skill published in the GitHub repository hachej/boring-ui (46 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 589 once invoked, about $0.0002 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
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-sync-helper
General GitHub basic operations + automation for GitHub platform objects (Issues/Labels/Milestones/Releases/Actions) in the Minis environment. This skill must be triggered when the user mentions any basic Git/GitHub operation or workflow, including "how to use GitHub," clone, init, remote, branch, commit, push, pull…