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 skills/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/skills/fu-jie/openwebui-extensions/release-prep)<a href="https://agentmods.dev/skills/fu-jie/openwebui-extensions/release-prep"><img src="https://agentmods.dev/badge/skills/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/skills/fu-jie/openwebui-extensions/release-prep"><img src="https://agentmods.dev/badge/skills/fu-jie/openwebui-extensions/release-prep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 27 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00056 | $0.01571 |
| Opus 5.5 | $0.00022 | $0.00628 |
| Sonnet 5.5 | $0.00011 | $0.00314 |
| Haiku 4.5 | $0.00006 | $0.00157 |
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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Prep
Overview
This skill drives the complete pre-PR release pipeline. It enforces the repository rule that every release must synchronize the version number and changelog across at least 7 locations before a commit is created.
Scope
This skill covers:
- Version sync (delegates detail to
version-bumperif needed) - Bilingual release notes file creation
- 7-location consistency verification
- Conventional Commits message drafting
git add -A && git commitexecution
It stops before git push or gh pr create. Use the pr-submitter skill for those steps.
Temporary File Convention
Any temporary files created during release prep (e.g., draft changelogs) must:
- Be written to the project's
.temp/directory, NOT system/tmp - Be cleaned up before commit using
rm -f .temp/file_name - Never be committed to git (add
.temp/to.gitignore)
Workflow
Step 1 — Collect Release Info
Ask the user (or infer from current state) the following:
- Plugin name and type (actions / filters / pipes / tools)
- New version number (e.g.,
0.8.0) - Key changes in English and Chinese (1-5 bullet points each)
If a What's New section already exists in README.md, extract it as the source of truth.
Step 2 — Sync Version Across 7 Locations
Verify AND update the version string in all of the following. Mark each as ✅ or ❌:
| # | File | Location |
|---|---|---|
| 1 | plugins/{type}/{name}/{name}.py |
version: in docstring |
| 2 | plugins/{type}/{name}/README.md |
**Version:** x.x.x metadata line |
| 3 | plugins/{type}/{name}/README_CN.md |
**Version:** x.x.x metadata line |
| 4 | docs/plugins/{type}/{name}.md |
**Version:** x.x.x metadata line |
| 5 | docs/plugins/{type}/{name}.zh.md |
**Version:** x.x.x metadata line |
| 6 | docs/plugins/{type}/index.md |
version badge for this plugin |
| 7 | docs/plugins/{type}/index.zh.md |
version badge for this plugin |
Additionally update the root-level updated date badge in:
README.md—README_CN.md— same badge format
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 · 158 lines · 56 tokens per session scan A 947fc152337e
release-prep is a skill published in the GitHub repository Fu-Jie/openwebui-extensions (327 stars, last pushed 10d ago), licensed MIT. It adds 56 tokens to every session and 1,571 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 skills, from other repositories
gsd-complete-milestone
Archive completed milestone and prepare for next version.
github-ops
GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.
release
Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.
update
Safe cc10x upgrade through the Claude Code plugin CLI. Lists every installed scope, refreshes the marketplace, updates each scope, and optionally carries local patches over to the new install. Use this skill when: updating cc10x, upgrading, pulling latest cc10x, syncing plugin, refreshing cache, or checking for new…
03-release-tag
Cut a semver release with an annotated tag and release notes. Use when the user wants to release, tag a release, bump the version, or cut a version. Not for a plain commit, a pull request, or amending an existing tag.
mcp-release-prep
Prepare an MCP server and plugin release by bumping versions across all files and updating changelog.