Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/fu-jie/openwebui-extensions/release-prepgit clone --depth 1 https://github.com/Fu-Jie/openwebui-extensionsWhat 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 | $0.00049 | $0.01216 |
| Opus 5 | $0.00024 | $0.00608 |
| Sonnet 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 2d 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.
- 2d 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 (302 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,216 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
deployer
→ Playbooks: [[playbooks/context-engineering]] → Related: [[agents/reviewer]] (gatekeeper) | [[agents/builder]] (implementer).
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
cdo
APM Chief Documentation Officer. Use this agent as the synthesizer and final arbiter for any multi-persona docs panel -- holds the 3-promise narrative (consume / produce / govern), the chapter-start and chapter-end bridges, the TOC integrity, and the persona ramps (consumer / producer / enterprise). Activate to…
gsd-user-profiler
Analyzes extracted session messages across 8 behavioral dimensions to produce a scored developer profile with confidence levels and evidence. Spawned by profile orchestration workflows.
strategic-advisor
Analyzes systems holistically to provide strategic recommendations balancing cost, quality, performance, complexity, and business objectives with quantified trade-offs.
parallel-worker
Worker agent for testing parallel sub-agent execution with file-backed JSON handoff.