Omnigent is an open-source orchestration layer for running and coordinating different AI coding agents through one system. It is for developers who want to combine agents, apply policies and sandboxing, and continue sessions across devices. The catalogue add-ons extend its agent workflows.
Borrowing it
Nothing to install: this file belongs to omnigent-ai/omnigent. 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/omnigent-ai/omnigent/main/.claude/skills/draft-release-notes/SKILL.mdgit clone --depth 1 https://github.com/omnigent-ai/omnigentWrote 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/omnigent-ai/omnigent/draft-release-notes)<a href="https://agentmods.dev/skills/omnigent-ai/omnigent/draft-release-notes"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/draft-release-notes/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/omnigent-ai/omnigent/draft-release-notes"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/draft-release-notes.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.00059 | $0.01999 |
| Opus 5.5 | $0.00024 | $0.00800 |
| Sonnet 5.5 | $0.00012 | $0.00400 |
| Haiku 4.5 | $0.00006 | $0.00200 |
Grade A, and why
draft-release-notes 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 15d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft the next Omnigent release notes
Produce a reviewable release-note draft and a complete changelog preview for a specific version and commit range. Use the repository's existing generation contract and keep the result unpublished. A drafting request covers the preview workflow and local artifacts; tags, version bumps, changelog PRs, and GitHub Release writes require a request for those actions.
Run commands from an Omnigent checkout with Git history, authenticated gh, and
Python 3.11+ with packaging. Preserve unrelated changes; use an isolated
worktree of the trusted default branch if the current checkout differs.
Resolve the inputs
Read the current sources before drafting; their contract takes precedence over the examples below:
.github/workflows/draft-release-notes.yml: preview inputs and artifacts..github/agents/release-notes-drafter/config.yaml: highlight format and voice..github/scripts/changelog/generate.py: release range, PR harvest, and credits..github/scripts/changelog/compose_notes.py: citation validation and footer.
Inspect a recent final GitHub Release for editorial style. Use the version and
cutoff requested by the user. If omitted, infer the next version from
pyproject.toml and final releases and state that assumption; ask only if those
sources leave materially different choices.
When refreshing a reviewed draft, read it first and generate a separate candidate. Preserve the user's editorial scope, wording, and verified contributor additions unless the new range or their instructions require a change; regenerating from raw highlights can otherwise discard those edits.
Refresh remote refs and tags. Select the previous final vX.Y.Z tag using
generate.previous_final_tag and the intended version, rather than the newest
nightly/RC tag or release publication date. Honor an explicit base override.
For an uncut release, pin the current remote main SHA, or the user's chosen
cutoff, as the range head. For an existing release tag, use its commit. Do not
create a tag just to make the generator accept the upcoming version.
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.
- 15d ago First seen · 184 lines · 59 tokens per session scan A c94fadbf96b7
draft-release-notes is a skill published in the GitHub repository omnigent-ai/omnigent (11,100 stars, last pushed today), licensed Apache-2.0. It adds 59 tokens to every session and 1,999 once invoked, about $0.0002 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-10-14.
Other skills, from other repositories
changelog
Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation collapse (merging X.Y.Z-rc. sections into a single X.Y.Z section). Invoke before tagging a release.
jira-release
Assemble a release from a batch of Jira issues — one release branch, pull request, preview and tracking issue per repository — and, when a person says to ship it, merge it and move the cards on. Insert into the prompt of a run started on a batch of issues.
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
ship
Enter the Ship phase of CocoBrew. Reads review.md approval, generates structured commit, creates semantic version tag, optionally creates PR via gh CLI, and records deployment details. Requires approved review.
release-management
Automates GitHub releases with semantic versioning, changelog generation from merged PRs, and gh CLI integration. Supports draft, prerelease, and standard release workflows with task-tracked multi-phase execution. Use when creating releases, tagging versions, or publishing changelogs.
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.