boring-ui: Skill for Claude Code

.agents/skills/owner-gate/SKILL.md

owner-gate is a skill for Claude Code from hachej/boring-ui. It costs 22 tokens per session (1,813 once invoked), scanned A, original, MIT.

A skill that raises a formal request for the owner to decide at a required project checkpoint.

In plain words
What is it for?
Use it for plan approval or merge approval, including the relevant plan, proof, risk, commit, and target branch details.
Why use it?
It prevents the agent from continuing past decisions that require human intent or approval.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is hachej/boring-ui's own configuration. It tells Claude Code how to work on boring-ui itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything boring-ui configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/hachej/boring-ui/main/.agents/skills/owner-gate/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/hachej/boring-ui

Made for: Claude Code.

Wrote 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.

agentmods badge for owner-gate

README.md
[![agentmods](https://agentmods.dev/badge/skills/hachej/boring-ui/owner-gate.svg)](https://agentmods.dev/skills/hachej/boring-ui/owner-gate)
Your own site
<a href="https://agentmods.dev/skills/hachej/boring-ui/owner-gate"><img src="https://agentmods.dev/badge/skills/hachej/boring-ui/owner-gate.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,813 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.01813
Opus 5 $0.00011 $0.00907
Sonnet 5 $0.00004 $0.00363
Haiku 4.5 $0.00002 $0.00181

Measured yesterday against content hash 7c09cb681037, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

owner-gate 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 yesterday.

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.

.agents/skills/owner-gate/SKILL.md · 159 lines

How it starts

The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Owner gate

A factory gate is a point where the owner decides and the seat must not proceed. There is exactly one transport: the ask_user tool, which raises an Inbox Human Intention and blocks your turn until the owner answers. docs/procedures/owner-review-card.md says WHAT to put in front of the owner; this says HOW it reaches them.

Never substitute a chat message, a bead comment, or a "let me know" for a gate. A gate that did not become an inbox item did not happen.

Titles follow docs/procedures/naming-conventions.md: [Feature Name] Plan approval / [Feature Name] Merge approval — never lead with a bead id.

The two gates

The visual is mandatory at both gates, not optional — read ../show-me/SKILL.md for its view-selection table before producing either artifact below.

  • Gate 1 — plan approval (Orchestrator). Raised after the Bead graph is materialized and the adversarial plan review is done, never before. Links the plan doc. Also write docs/issues/<issue>/show-me-plan.md with at most three views selected from show-me's table: the structure view (a shallow file tree or component tree of what the epic touches), the behavior view (a call tree or mermaid sequence of the new flow), and a diff-shaped view of what changes in the existing shape. Pass it as an artifacts[] entry:

    {
      "id": "show-me-plan",
      "surfaceKind": "workspace.open.path",
      "target": "docs/issues/<issue>/show-me-plan.md",
      "title": "[Feature Name] Plan, visually"
    }
    

    context still starts with the one-sentence line; the show-me artifact adds to it, never replaces it.

  • Gate 2 — merge approval (Orchestrator). Raised once every epic Bead is handed off (per factory_status or its equivalent): open or update the epic PR (title [Feature Name] <what changed>, body = the Owner Review card from docs/procedures/owner-review-card.md, then a ## Show me section, then ## Handover), start a demo_sandbox at the exact SHA when that tool is available, and put its URL on the card's Artifact: line and again in context with its expiry. Must name the exact SHA and the expected target head. The ## Show me section carries diff-shaped views (component/call/file tree diff) plus one sequence diagram of the shipped flow, derived from the actual commits — never from memory of the plan. Write the same views to docs/issues/<issue>/show-me-<short sha>.md and pass it as an artifact next to the present-pr artifact when one exists:

Read the full file on GitHub · 159 lines

Changes

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.

  1. yesterday Changed · +53 lines 7c09cb681037
  2. 3d ago First seen · 106 lines · 22 tokens per session scan A a001dc51b889

Subscribe to this mod's changes

owner-gate is a skill published in the GitHub repository hachej/boring-ui (46 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 1,813 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-09-03.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens