Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Jarroslav/agentic-os/plugin install agentic-sdlcWrote 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/jarroslav/agentic-os/release-manager)<a href="https://agentmods.dev/skills/jarroslav/agentic-os/release-manager"><img src="https://agentmods.dev/badge/skills/jarroslav/agentic-os/release-manager/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/jarroslav/agentic-os/release-manager"><img src="https://agentmods.dev/badge/skills/jarroslav/agentic-os/release-manager.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.00140 | $0.02938 |
| Opus 5.5 | $0.00056 | $0.01175 |
| Sonnet 5.5 | $0.00028 | $0.00588 |
| Haiku 4.5 | $0.00014 | $0.00294 |
Grade A, and why
release-manager 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 2mo 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release-manager
Cross-reference the commits that landed in a release range against the tickets tagged with that release's fix version, then print a bidirectional gap report. The audit surfaces the two failure modes teams miss before a cut: tickets in the fix version with no commit behind them, and commits that shipped without a ticket (or against a ticket the fix version excludes).
Blast radius R0. This skill only reads — git history, remote tags, and the ticket tracker via its adapter. It creates no tags, no tickets, no releases, and never edits a fix version. It recommends changes in the report and stops.
Adapter-driven: no ticket backend is hardcoded. The tracker is resolved from
.agentic/guides/project.md and ${CLAUDE_PLUGIN_ROOT}/references/work-item-adapters.md.
Anything beyond Jira / GitHub Issues / GitLab Issues requires a custom adapter
declaration.
Stored variables
| Variable | Meaning |
|---|---|
repos |
Repos to scan (paths or owner/repo slugs) |
fix_version_label |
Full release label verbatim — used for fix-version queries |
release_version |
Bare semver extracted from the label — used for tag lookup/comparison |
ticket_provider |
jira | github | gitlab | none |
project_key |
Tracker project key (e.g. a Jira project prefix) |
vcs_tool |
Per-repo CLI: gh | glab | git-only |
prev_tag |
Lower bound of the commit range |
current_tag |
Upper bound of the commit range |
tickets |
Fetched ticket records |
commits |
Collected commit records |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 309 lines · 140 tokens per session scan A 1ee3fa4be822
release-manager is a skill published in the GitHub repository Jarroslav/agentic-os (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 140 tokens to every session and 2,938 once invoked, about $0.0006 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-31.
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.
updater_guide
Is Row-Bot up to date? Checking for and installing Row-Bot updates.