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/Comfy-Org/workflow_templatesnpx agentmods add skills/comfy-org/workflow_templates/managing-releasesWrote 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/comfy-org/workflow_templates/managing-releases)<a href="https://agentmods.dev/skills/comfy-org/workflow_templates/managing-releases"><img src="https://agentmods.dev/badge/skills/comfy-org/workflow_templates/managing-releases/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/comfy-org/workflow_templates/managing-releases"><img src="https://agentmods.dev/badge/skills/comfy-org/workflow_templates/managing-releases.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00155 | $0.02344 |
| Opus 5 | $0.00077 | $0.01172 |
| Sonnet 5 | $0.00031 | $0.00469 |
| Haiku 4.5 | $0.00015 | $0.00234 |
Grade A, and why
managing-releases 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 9d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing Releases
How this repository turns template changes into version bumps → PyPI packages → GitHub releases. The short version: version bumps happen on the PR (author-driven + CI auto-bump); publishing happens after merge (label-driven); every merge with a version change creates a GitHub Release, but PyPI publish requires the release label.
The two workflows (read these first)
| Workflow | Phase | Trigger | What it does |
|---|---|---|---|
version-check.yml |
On the PR | PR touching templates/**, bundles.json, blueprints/**, pyproject.toml, version policy files |
Syncs manifests, validates bundles, auto-bumps package versions (only when root version changed), posts PyPI quota + release-distribution comments, commits changes back to the PR branch |
publish.yml |
After merge | Push to main with pyproject.toml changes, or manual dispatch |
Checks the merged PR for the release label, runs PyPI quota gate, builds & publishes affected packages in dependency order, always creates a GitHub Release |
Version bump model (how versions move)
- Root
pyproject.toml(themetapackage) is manually controlled by the PR author. CI never auto-bumps it. - Sub-packages (
core,json,media_api,media_video,media_image,media_other,media_assets_01,blueprints) are auto-bumped byci_version_manager.py— but only when the PR author has changed the root version. - Template-only PRs (root version unchanged): no version bumps at all — manifests still get re-synced and committed.
| PR type | Auto-bump? | PyPI after merge? |
|---|---|---|
| Template / archive only (root version unchanged) | ❌ None | ❌ No (no version change → publish.yml not triggered on pyproject.toml) |
Release PR (author bumps root version) without release label |
✅ Sub-packages | ❌ GitHub Release only |
Release PR (author bumps root version) with release label |
✅ Sub-packages | ✅ Full PyPI publish + GitHub Release |
Manual workflow_dispatch with force_publish=true |
— | ✅ Bypasses label; publishes packages whose local version ≠ PyPI |
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.
- 9d ago First seen · 135 lines · 155 tokens per session scan A c2458ac43f1c
managing-releases is a skill published in the GitHub repository Comfy-Org/workflow_templates (884 stars, last pushed yesterday), licensed MIT. It adds 155 tokens to every session and 2,344 once invoked, about $0.0008 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-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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
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.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.