Borrowing it
Nothing to install: this file belongs to mendix/web-widgets. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mendix/web-widgets/main/.agents/skills/release-widget/SKILL.mdgit clone --depth 1 https://github.com/mendix/web-widgetsWrote 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/mendix/web-widgets/release-widget)<a href="https://agentmods.dev/skills/mendix/web-widgets/release-widget"><img src="https://agentmods.dev/badge/skills/mendix/web-widgets/release-widget/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/mendix/web-widgets/release-widget"><img src="https://agentmods.dev/badge/skills/mendix/web-widgets/release-widget.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.00065 | $0.03177 |
| Opus 5.5 | $0.00026 | $0.01271 |
| Sonnet 5.5 | $0.00013 | $0.00635 |
| Haiku 4.5 | $0.00006 | $0.00318 |
Grade A, and why
release-widget 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 today.
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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Widget
Overview
Releases a widget (or the module wrapping it): version bump → GitHub draft release → OSS clearance → Marketplace publish.
Autonomy carve-out (this skill only): pre-authorized to run git push, gh workflow run, and gh release edit --draft=false (publish) directly without per-step confirmation. Does not extend to rollback (deleting releases/tags/branches) or merging PRs (branch protection needs team approvals — user's job).
No persisted release-state file — each invocation re-checks git/GitHub/Jira/Marketplace from scratch. Safe to stop and resume across sessions.
Prerequisites
Ask only if not already known:
- Package name — widget or module to release, e.g.
combobox-webordata-widgets. If not given, ask: "Which widget or module are you releasing?"
Everything else — check automatically in Phase 0, don't ask.
Workflow
Phase 0 — Detect release target
cd packages/pluggableWidgets/<widget>
pnpm exec rui-package-info
Prints {"name", "version", "appNumber", "appName"}. Reads process.cwd() — always cd into the widget/module dir first, never pass a path argument.
appName is the Marketplace display name (e.g. Maps). Draft release is titled <appName> v<version>.
appNumberpositive → standalone release. Keep thisinfo— Phase 2/3 reuse<npm-package-name>from it, Phase 7 reusesappNumber.appNumberisnull/absent/-1→ widget is wrapped by another package. Find the owner (usually a module, but a widget likecharts-webalso wraps sub-widgets e.g.area-chart-web):
No owner found → stop, package is misconfigured. Otherwise re-run from the owner's directory:grep -l "\"@mendix/<widget>\"" packages/modules/*/package.json packages/pluggableWidgets/*/package.json
Owner'scd packages/modules/<owner> # or packages/pluggableWidgets/<owner> pnpm exec rui-package-infoinfois the release target from here on. Tell the user which module or widget wraps it.
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.
- today Changed bb0fd513bb74
- 1mo ago First seen · 242 lines · 65 tokens per session scan A 970646cc8d9a
release-widget is a skill published in the GitHub repository mendix/web-widgets (40 stars, last pushed today), licensed Apache-2.0. It adds 65 tokens to every session and 3,177 once invoked, about $0.0003 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-09-19.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.