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/owner-gate/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/owner-gate)<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>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.00022 | $0.01813 |
| Opus 5 | $0.00011 | $0.00907 |
| Sonnet 5 | $0.00004 | $0.00363 |
| Haiku 4.5 | $0.00002 | $0.00181 |
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.
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.mdwith 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 anartifacts[]entry:{ "id": "show-me-plan", "surfaceKind": "workspace.open.path", "target": "docs/issues/<issue>/show-me-plan.md", "title": "[Feature Name] Plan, visually" }contextstill 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_statusor its equivalent): open or update the epic PR (title[Feature Name] <what changed>, body = the Owner Review card fromdocs/procedures/owner-review-card.md, then a## Show mesection, then## Handover), start ademo_sandboxat the exact SHA when that tool is available, and put its URL on the card'sArtifact:line and again incontextwith its expiry. Must name the exact SHA and the expected target head. The## Show mesection 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 todocs/issues/<issue>/show-me-<short sha>.mdand pass it as an artifact next to the present-pr artifact when one exists:
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.
- yesterday Changed · +53 lines 7c09cb681037
- 3d ago First seen · 106 lines · 22 tokens per session scan A a001dc51b889
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.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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…
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.
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.