openwebui-extensions: Instructions file for Kiro

.kiro/steering/release-prep.md

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

A release-preparation workflow for a plugin that updates version details, writes release notes in English and Chinese, checks consistency, and drafts a commit.

In plain words
What is it for?
Use it to prepare a plugin release, synchronize details across repository files, and create a Conventional Commits message, a standard format for commit messages.
Why use it?
It reduces missed version or documentation updates before a pull request (a proposed code change for review). It stops before pushing code or opening the pull request.

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 →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/check_version_consistency.py.

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

README.md
[![agentmods](https://agentmods.dev/badge/instructions/fu-jie/openwebui-extensions/release-prep/github.svg)](https://agentmods.dev/instructions/fu-jie/openwebui-extensions/release-prep)
Your own site
<a href="https://agentmods.dev/instructions/fu-jie/openwebui-extensions/release-prep"><img src="https://agentmods.dev/badge/instructions/fu-jie/openwebui-extensions/release-prep/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-prep

Your own site · 80×15
<a href="https://agentmods.dev/instructions/fu-jie/openwebui-extensions/release-prep"><img src="https://agentmods.dev/badge/instructions/fu-jie/openwebui-extensions/release-prep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 592 This file is loaded in full into every session.
When invoked 592 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.00592 $0.00592
Opus 5.5 $0.00237 $0.00237
Sonnet 5.5 $0.00118 $0.00118
Haiku 4.5 $0.00059 $0.00059

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

Security

Grade A, and why

release-prep 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-prep.md · 77 lines

How it starts

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

Release Prep

Overview

Drives the complete pre-PR release pipeline. Enforces that every release synchronizes the version number and changelog across at least 7 locations before a commit is created.

Scope

This skill covers:

  1. Version sync (delegates detail to version-bumper if needed)
  2. Bilingual release notes file creation
  3. 7-location consistency verification
  4. Conventional Commits message drafting
  5. git add -A && git commit execution

It stops before git push or gh pr create. Use the pr-submitter skill for those steps.


Workflow

Step 1 — Collect Release Info

  • Plugin name and type (actions / filters / pipes / tools)
  • New version number (e.g., 0.8.0)
  • Key changes in English and Chinese

Step 2 — Sync Version Across 7 Locations

# File Location
1 plugins/{type}/{name}/{name}.py version: in docstring
2 plugins/{type}/{name}/README.md metadata line
3 plugins/{type}/{name}/README_CN.md metadata line
4 docs/plugins/{type}/{name}.md metadata line
5 docs/plugins/{type}/{name}.zh.md metadata line
6 docs/plugins/{type}/index.md version badge
7 docs/plugins/{type}/index.zh.md version badge

Step 3 — Update What's New (All 4 Doc Files)

Only the most recent release's changes. Previous entries removed.

Step 4 — Create Bilingual Release Notes Files

  • plugins/{type}/{name}/v{version}.md
  • plugins/{type}/{name}/v{version}_CN.md

Step 5 — Verify Consistency

python3 scripts/check_version_consistency.py

Step 6 — Draft Conventional Commits Message

English only. Format: type(scope): subject

Step 7 — Stage and Commit

git add -A
git commit -m "<approved commit message>"

Anti-Patterns to Avoid

  • ❌ Do NOT add extra features during release prep
  • ❌ Do NOT push or create PR in this skill — use pr-submitter
  • ❌ Do NOT leave stale What's New content from prior versions

Read the full file on GitHub · 77 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. 26d ago First seen · 77 lines · 592 tokens per session scan A ca2b75154db8

Subscribe to this mod's changes

release-prep is an instructions file published in the GitHub repository Fu-Jie/openwebui-extensions (333 stars, last pushed 27d ago), licensed MIT. It adds 592 tokens to every session, about $0.0024 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-prep compared with instructions from other repositories

release-prep next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
release-prepFu-Jie/openwebui-extensionsInstructions file33327d agoMITA592Kiro
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