Obot is an open-source platform that helps organizations manage, secure, and govern AI clients, models, tools, MCP servers, skills, credentials, and hosted workloads. It is for teams that need controlled access, identity and permissions, sandboxed execution, registries, and audit records across agents such as Claude Code, Codex, Cursor, and IDE tools. The catalogue entries supply skills and instructions that can be managed or used within the Obot platform.
Borrowing it
Nothing to install: this file belongs to obot-platform/obot. 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/obot-platform/obot/main/.claude/skills/draft-release/SKILL.mdgit clone --depth 1 https://github.com/obot-platform/obotWrote 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/obot-platform/obot/draft-release)<a href="https://agentmods.dev/skills/obot-platform/obot/draft-release"><img src="https://agentmods.dev/badge/skills/obot-platform/obot/draft-release/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/obot-platform/obot/draft-release"><img src="https://agentmods.dev/badge/skills/obot-platform/obot/draft-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 231 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00078 | $0.04350 |
| Opus 5.5 | $0.00031 | $0.01740 |
| Sonnet 5.5 | $0.00016 | $0.00870 |
| Haiku 4.5 | $0.00008 | $0.00435 |
Grade A, and why
draft-release 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft Release Notes
Drafts release notes for the next obot minor release and creates a draft (unpublished) GitHub release containing them. The release stays in draft state for the user to review, edit, and publish themselves. Never creates the git tag, never publishes the release, never pushes anything.
Inputs
- Target version (e.g.
v0.22.0): ask the user if not provided. If recent pre-release tags exist (e.g.v0.22.0-rc3), suggest the corresponding minor (v0.22.0) and confirm. - Diff baseline (e.g.
v0.21.3): auto-detect as the highest non-pre-release tag, regardless of whether it is a minor or patch, that is also an ancestor ofHEAD. This is the range used to find changes (<DIFF_BASELINE>..HEAD) and the left side of the "Full Changelog" compare link. Usegit tag --sort=-v:refname | grep -v -- '-' | head -1, then verify withgit merge-base --is-ancestor <candidate> HEAD. Patch releases are sometimes cut from a separate release branch that never merges back intomain— if the highest-sorted tag fails the ancestor check, walk down to the next-highest tag and check again until one passes. Do not silently trust version-sort order alone. - Style reference (e.g.
v0.21.0): auto-detect as the highestvX.Y.0tag that is not a pre-release. Usegit tag --list 'v*.*.0' --sort=-v:refname | grep -v -- '-' | head -1. This release's notes are the tone/structure template. It is often the same as the diff baseline but may differ when patch releases exist between minors.
Hard constraints
- Do NOT create git tags. Do NOT run
git tagorgit push --tags. The draft release does not require the tag to exist locally — GitHub creates it only when the draft is published, which the user does manually. gh release createis allowed ONLY with--draft. Never run it without--draft. Never rungh release edit --draft=false. Never publish.- Do NOT model the notes on patch releases (
vX.Y.Zwhere Z > 0) or pre-releases (-rc,-alpha,-beta). Those use minimal notes. Always model on the most recentvX.Y.0. - No emojis. No em dashes (
—). Use plain hyphens or rewrite the sentence. No "we're thrilled / excited to / proud to" beyond the one opening line the template already uses. No marketing fluff. - Use straight quotes (
'and"), not curly quotes. - Do not invent PRs, authors, or commit messages in "What's Changed". That section must be sourced from the GitHub API, not synthesized.
- Never run
gh release create(or any other command that writes to GitHub) until the user has seen the fully assembled draft (opener, Big Updates, Improvements, Upgrade Notes, What's Changed, Full Changelog line — the whole document, not just the feature list from step 5) and explicitly approved it. Step 5's feature-list confirmation is necessary but not sufficient; the user must sign off on the actual prose before anything is pushed to GitHub.
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 · 248 lines · 78 tokens per session scan A 083c30e5f15b
draft-release is a skill published in the GitHub repository obot-platform/obot (1,167 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 4,350 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-08-30.
draft-release compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| draft-releaseobot-platform/obot | Skill | 1.2k | yesterday | MIT | A | 78 | Claude Code |
| oma-scmgracefullight/docusaurus-plugins | Skill | 23 | 1mo ago | MIT | A | 37 | Claude Code, Codex |
| releasethedotmack/claude-mem | Skill | 114k | yesterday | Apache-2.0 | A | 13 | Claude Code |
| release-notesphuryn/pm-skills | Skill | 28k | 8d ago | MIT | A | 57 | Claude Code |
| multi-agent-release-managerchromium/chromium | Skill | 25k | yesterday | BSD-3-Clause | A | 27 | Claude Code, Codex |
| pack-submitaeonfun/aeon | Skill | 788 | yesterday | MIT | A | 27 | Claude Code, Codex |
| updater_guidesiddsachar/row-bot | Skill | 1.7k | today | Apache-2.0 | A | 22 | Claude Code, Codex |