openwebui-extensions: Instructions file for Kiro

.kiro/steering/release-finalizer.md

release-finalizer is an instructions file for Kiro from Fu-Jie/openwebui-extensions. It costs 390 tokens per session, scanned A, original, MIT.

A release-finalization workflow that verifies an open pull request, merges it, links related issues, replies to their reporters, and closes them.

In plain words
What is it for?
Use it after review to check status checks, choose a squash merge, delete the branch, post issue updates, and close resolved issues.
Why use it?
It prevents merging before required checks and review work are complete. It also keeps the pull request and its related issue records connected.

Instructions file for Kiro

Written for Kiro: installed under .kiro/.

This is Fu-Jie/openwebui-extensions's own configuration. It tells Kiro how to work on openwebui-extensions 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 openwebui-extensions configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Fu-Jie/openwebui-extensions. 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/Fu-Jie/openwebui-extensions/main/.kiro/steering/release-finalizer.md
Clone the repo
git clone --depth 1 https://github.com/Fu-Jie/openwebui-extensions

Made for: Kiro.

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 release-finalizer

README.md
[![agentmods](https://agentmods.dev/badge/instructions/fu-jie/openwebui-extensions/release-finalizer/github.svg)](https://agentmods.dev/instructions/fu-jie/openwebui-extensions/release-finalizer)
Your own site
<a href="https://agentmods.dev/instructions/fu-jie/openwebui-extensions/release-finalizer"><img src="https://agentmods.dev/badge/instructions/fu-jie/openwebui-extensions/release-finalizer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for release-finalizer

Your own site · 80×15
<a href="https://agentmods.dev/instructions/fu-jie/openwebui-extensions/release-finalizer"><img src="https://agentmods.dev/badge/instructions/fu-jie/openwebui-extensions/release-finalizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 390 This file is loaded in full into every session.
When invoked 390 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00390 $0.00390
Opus 5.5 $0.00156 $0.00156
Sonnet 5.5 $0.00078 $0.00078
Haiku 4.5 $0.00039 $0.00039

Measured 26d ago against content hash caa779e2bae1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-finalizer 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 26d 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.

.kiro/steering/release-finalizer.md · 58 lines

What it actually says

Release Finalizer

Overview

Completes the final step of the release cycle: merging the release PR to main, replying to all related issues with solutions, and automatically closing them.

Prerequisites

  • The PR is in OPEN state and ready to merge
  • All status checks have passed
  • All review feedback has been addressed

Workflow

Step 1 — Pre-Merge Verification

PAGER=cat GH_PAGER=cat gh pr view <PR-NUMBER> --json state,statusCheckRollup,reviewDecision

Step 2 — Identify Related Issues

Look for Closes #XX, Fixes #XX, Resolves #XX in PR description and commits.

Step 3 — Select Merge Strategy

Default: --squash for release PRs.

Step 4 — Execute Merge

gh pr merge <PR-NUMBER> \
  --squash \
  --delete-branch \
  -m "type(scope): description" \
  -b "- Bullet 1\n\nCloses #48"

Step 5 — Post Closing Message

gh issue comment <ISSUE-NUMBER> --body "This has been fixed in PR #<PR-NUMBER>. Thank you for reporting! ⭐"

Anti-Patterns to Avoid

  • ❌ Do NOT merge if any status checks are PENDING or FAILED
  • ❌ Do NOT merge without Closes #XX keywords for related issues
  • ❌ Do NOT delete the branch if it might be needed for cherry-pick
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. 26d ago First seen · 58 lines · 390 tokens per session scan A caa779e2bae1

Subscribe to this mod's changes

release-finalizer is an instructions file published in the GitHub repository Fu-Jie/openwebui-extensions (333 stars, last pushed 27d ago), licensed MIT. It adds 390 tokens to every session, about $0.0016 per session on Opus 5.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-10-11.

Related

release-finalizer compared with instructions from other repositories

release-finalizer next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
release-finalizerFu-Jie/openwebui-extensionsInstructions file33327d agoMITA390Kiro
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode