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 skills/fu-jie/openwebui-extensions/release-finalizernpx skills add Fu-Jie/openwebui-extensions --skill release-finalizergit clone --depth 1 https://github.com/Fu-Jie/openwebui-extensionsWrote 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-finalizer)<a href="https://agentmods.dev/skills/fu-jie/openwebui-extensions/release-finalizer"><img src="https://agentmods.dev/badge/skills/fu-jie/openwebui-extensions/release-finalizer.svg" alt="Measured on agentmods" 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.00042 | $0.01570 |
| Opus 5 | $0.00021 | $0.00785 |
| Sonnet 5 | $0.00008 | $0.00314 |
| Haiku 4.5 | $0.00004 | $0.00157 |
Grade A, and why
release-finalizer 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 6d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Finalizer
Overview
This skill completes the final step of the release cycle: merging the release PR to main, replying to all related issues with solutions, and automatically closing them using GitHub's issue linking mechanism.
Prerequisites
- The PR is in
OPENstate and ready to merge - All status checks have passed (CI green)
- All review feedback has been addressed
- The PR relates to one or more GitHub issues (either in PR description or through commits)
Workflow
Step 1 — Pre-Merge Verification
Verify that the PR is ready:
PAGER=cat GH_PAGER=cat gh pr view <PR-NUMBER> --json state,statusCheckRollup,reviewDecision
Checklist:
- ✅
stateisOPEN - ✅
statusCheckRollupall haveconclusion: SUCCESS - ✅
reviewDecisionisAPPROVEDor empty (no blocking reviews)
If any check fails, do NOT merge. Report the issue to the user.
Step 2 — Identify Related Issues
Issues can be linked to a PR in multiple ways. Check the PR description and commit messages for keywords:
PAGER=cat GH_PAGER=cat gh pr view <PR-NUMBER> --json body,commits
Look for patterns like:
Closes #XX,Fixes #XX,Resolves #XX(in description or commit bodies)#XXmentioned as "related to" or "addresses"
Manual input: If issue links are not in the PR, ask the user which issue(s) this PR resolves.
Extract all issue numbers into a list: [#48, #52, ...]
Step 3 — Select Merge Strategy
Offer the user three options:
| Strategy | Git Behavior | Use Case |
|---|---|---|
| Squash | All commits squashed into one commit on main | Clean history, recommended for release PRs |
| Rebase | Linear history, no merge commit | Preserve commit granularity |
| Merge | Merge commit created | Preserve full PR context |
Recommendation for release PRs: Use --squash to create a single clean commit.
If user doesn't specify, default to --squash.
Step 4 — Prepare Merge Commit Message
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.
- 6d ago First seen · 209 lines · 42 tokens per session scan A 8c85c9c4792c
release-finalizer is a skill published in the GitHub repository Fu-Jie/openwebui-extensions (304 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 1,570 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
release-openspec
Use this skill when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes. Also use when asked whether an open release PR is…
gsd-graphify
Build, query, and inspect the project knowledge graph in .planning/graphs/.
cut-release
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR…
handoff
Prepare a clean cross-session handoff so the next agent can pick up where you left off. Writes a focused continue.md in the active slice dir and ensures STATE.md + summary artifacts are current. Use when asked to "hand off", "prepare handoff", "pause work", "bookmark this", "I'll come back to this later", before…
user-general-facts
Capture and organize general facts about the user by topic.
daily-logs
Track daily activity logs and summaries for the user. TRIGGER BY: read/edit user memory.