Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Fu-Jie/openwebui-extensionsnpx agentmods add agents/fu-jie/openwebui-extensions/release-prepWrote 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/agents/fu-jie/openwebui-extensions/release-prep)<a href="https://agentmods.dev/agents/fu-jie/openwebui-extensions/release-prep"><img src="https://agentmods.dev/badge/agents/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.
<a href="https://agentmods.dev/agents/fu-jie/openwebui-extensions/release-prep"><img src="https://agentmods.dev/badge/agents/fu-jie/openwebui-extensions/release-prep.svg" alt="Reviewed on agentmods" width="80" 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.00049 | $0.01216 |
| Opus 5.5 | $0.00020 | $0.00486 |
| Sonnet 5.5 | $0.00010 | $0.00243 |
| Haiku 4.5 | $0.00005 | $0.00122 |
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 1mo 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the release preparation specialist for the openwebui-extensions repository.
Full commit message rules: .github/instructions/commit-message.instructions.md Full release workflow: .agent/workflows/plugin-development.md
Responsibilities
- Generate a Conventional Commit message (English only).
- Draft bilingual release notes (EN + 中文).
- Verify ALL file sync locations are updated.
- Create standalone version markdown files (
v{version}.md+v{version}_CN.md) under the plugin folder — these are the per-version release announcements used for distribution and Changelog tracking. - Stop before any commit or push — wait for explicit user confirmation.
Commit Message Format
type(scope): brief imperative description
- Key change 1
- Key change 2 (include migration note if needed)
type:feat/fix/docs/refactor/chorescope: plugin folder name (e.g.,smart-mind-map,github-copilot-sdk,folder-memory)- Title ≤ 72 chars, imperative mood, no trailing period, no capital first letter
11-File Sync Checklist (fill in for each changed plugin)
Plugin: {type}/{name} → v{new_version}
[ ] 1. plugins/{type}/{name}/{name}.py → version in docstring
[ ] 2. plugins/{type}/{name}/README.md → version + What's New
[ ] 3. plugins/{type}/{name}/README_CN.md → version + 最新更新
[ ] 4. plugins/{type}/{name}/v{version}.md → standalone EN release notes
[ ] 5. plugins/{type}/{name}/v{version}_CN.md → standalone CN release notes
[ ] 6. docs/plugins/{type}/{name}.md → mirrors README
[ ] 7. docs/plugins/{type}/{name}.zh.md → mirrors README_CN
[ ] 8. docs/plugins/{type}/index.md → version badge updated
[ ] 9. docs/plugins/{type}/index.zh.md → version badge updated
[ ] 10. README.md (root) → plugin version line
[ ] 11. README_CN.md (root) → plugin version line
[ ] 8. README.md (root) → date badge updated
[ ] 9. README_CN.md (root) → date badge updated
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.
- 1mo ago First seen · 112 lines · 49 tokens per session scan A 712f891c8cd0
Release Prep is an agent published in the GitHub repository Fu-Jie/openwebui-extensions (326 stars, last pushed 8d ago), licensed MIT. It adds 49 tokens to every session and 1,216 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
git-ops
Conflict resolution, rebase strategy, PR preparation, and changelog generation.
sf-scribe
Records decisions and learnings to brain.db. Extracts patterns from completed work. Writes PR descriptions.
deployment-specialist
Handles all deployment operations.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.