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/publish-no-version-bumpWrote 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/publish-no-version-bump)<a href="https://agentmods.dev/skills/fu-jie/openwebui-extensions/publish-no-version-bump"><img src="https://agentmods.dev/badge/skills/fu-jie/openwebui-extensions/publish-no-version-bump/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/publish-no-version-bump"><img src="https://agentmods.dev/badge/skills/fu-jie/openwebui-extensions/publish-no-version-bump.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 65 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.00040 | $0.00980 |
| Opus 5 | $0.00020 | $0.00490 |
| Sonnet 5 | $0.00008 | $0.00196 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
publish-no-version-bump 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 10d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish Without Version Bump
Overview
This skill handles the workflow for pushing code changes to the remote repository and syncing them to the OpenWebUI official marketplace without incrementing the plugin version number.
This is useful for:
- Bug fixes and patches
- Performance optimizations
- Code refactoring
- Documentation fixes
- Linting and code quality improvements
When to Use
Use this skill when:
- You've made non-breaking changes (bug fixes, optimizations, refactoring)
- The functionality hasn't changed significantly
- The user-facing behavior is unchanged or only improved
- There's no need to bump the semantic version
Do NOT use if:
- You're adding new features → use
release-prepinstead - You're making breaking changes → use
release-prepinstead - The version should be incremented → use
version-bumperfirst
Workflow
Step 1 — Stage and Commit Changes
Ensure all desired code changes are staged in git:
git status # Verify what will be committed
git add -A # Stage all changes
Create a descriptive commit message using Conventional Commits format:
fix(plugin-name): brief description
- Detailed change 1
- Detailed change 2
Example commit types:
fix:— Bug fixes, patchesperf:— Performance improvements, optimizationrefactor:— Code restructuring without behavior changetest:— Test updatesdocs:— Documentation changes
Key Rule: The commit message should make clear that this is NOT a new feature release (no feat: type).
Step 2 — Push to Remote
Push the commit to the main branch:
git commit -m "<message>" && git push
Verify the push succeeded by checking GitHub.
Step 3 — Publish to Official Marketplace
Run the publish script with --force flag to update the marketplace without version change:
python scripts/publish_plugin.py --force
Important: The --force flag ensures the marketplace version is updated even if the version string in the plugin file hasn't changed.
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.
- 10d ago First seen · 151 lines · 40 tokens per session scan A e20ca67eff7b
publish-no-version-bump is a skill published in the GitHub repository Fu-Jie/openwebui-extensions (307 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 980 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 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.
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.
github-release-guide
Assess and guide safer github.com repository releases. Use when an existing private GitHub repository becomes public for the first time, or whenever an already-public GitHub repository publishes a new version, and the user needs readiness checks, release-surface decisions, explicit mutation approvals, release notes…
mcp-release-prep
Prepare an MCP server and plugin release by bumping versions across all files and updating changelog.