ship-feature

ship-feature is a skill for Claude Code, Codex from openonion/connectonion. It costs 46 tokens per session (1,820 once invoked), scanned C, original, Apache-2.0.

A release workflow for completing a feature from code changes through tests, documentation, documentation-site updates, and publication to PyPI, Python's package repository.

In plain words
What is it for?
Use it when shipping or releasing a feature, updating its tests and docs, and publishing the result to PyPI.
Why use it?
It keeps the supporting work around a feature in sync before releasing a new version.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

About the project

ConnectOnion is an open-source, template-first toolkit for building, debugging, deploying, and operating AI agents. Developers use its command-line tools and Python runtime to create agents, add tools, connect services, deploy them, and make them callable by other agents, while the catalogue entries are related agents, skills, and instructions.

openonion/connectonion · 1,481 stars · on GitHub · docs.connectonion.com

Install

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.

agentmods
npx agentmods add skills/openonion/connectonion/ship-feature
Any agent
npx skills add openonion/connectonion --skill ship-feature
Clone the repo
git clone --depth 1 https://github.com/openonion/connectonion

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for ship-feature

README.md
[![agentmods](https://agentmods.dev/badge/skills/openonion/connectonion/ship-feature.svg)](https://agentmods.dev/skills/openonion/connectonion/ship-feature)
Your own site
<a href="https://agentmods.dev/skills/openonion/connectonion/ship-feature"><img src="https://agentmods.dev/badge/skills/openonion/connectonion/ship-feature.svg" alt="Measured on agentmods" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,820 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.01820
Opus 5 $0.00023 $0.00910
Sonnet 5 $0.00009 $0.00364
Haiku 4.5 $0.00005 $0.00182

Measured 6d ago against content hash da54238f0bd8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade C, and why

ship-feature scanned grade C with 1 finding 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 6d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf dist/
connectonion/useful_skills/ship-feature/SKILL.md · 191 lines

How it starts

The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ship Feature Skill

Ship a feature completely: tests → docs → docs-site → release.

Step 1: Understand What Changed

Read the user's message to identify which feature/module was changed.

Run in parallel:

  • git diff --stat — what files changed
  • git diff — full diff of changes
  • git log --oneline -5 — recent commit context

Step 2: Update Tests

Find the relevant test file:

  • glob("tests/**/*.py") — find all test files
  • Match test file to changed source file (e.g. src/agent.pytests/unit/test_agent.py)

Update the test file:

  • Add or update test cases that cover the new behavior
  • Run tests to confirm they pass: python -m pytest tests/unit/test_<module>.py -v
  • If tests fail, fix them before proceeding

Step 3: Update docs/

This step is required. Do not skip.

Find ALL docs that need updating:

glob("docs/**/*.md")

For each changed area:

  • If a doc file exists for it — update it with the new behavior, params, examples
  • If no doc file exists — create one (look at neighboring files for format)
  • Also check index/README files (e.g. docs/cli/README.md, docs/useful_tools/README.md) — update the table of contents if you added something new

Commit docs/ changes as part of the release commit (not separately).

Step 4: Update docs-site

This step is required. Do not skip even if docs-site/ is not present locally.

docs-site is a separate Next.js git repo. Check if it's cloned:

ls docs-site/

If docs-site/ exists:

  • Find the corresponding page: glob("docs-site/app/**/*.{tsx,mdx}")
  • Update it to match what you changed in docs/
  • Respect existing component structure (CommandBlock, CodeBlock, etc.)
  • Run its lint and production build. Prepare the docs commit, but do not publish version availability before the matching PyPI package and GitHub Release are public. Publish the prepared docs in Step 5e.

If docs-site/ does NOT exist locally:

  • Tell the user explicitly: "docs-site was not updated — clone it and run co copy ship-feature --force to re-run"
  • Do NOT silently skip — the user must know this is incomplete

Read the full file on GitHub · 191 lines

Changes

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.

  1. 6d ago First seen · 191 lines · 46 tokens per session scan C da54238f0bd8

Subscribe to this mod's changes

ship-feature is a skill published in the GitHub repository openonion/connectonion (1,481 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 1,820 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

release

Prepare and publish stable Agent Lightning releases through the repository's version bump, pull-request checks, merge, tag, PyPI trusted-publishing, and versioned-documentation workflows. Use when asked to plan, cut, verify, or explain a release; treat nightly TestPyPI builds as a separate path.

microsoft/agent-lightning · 63 tokens

git-changelog

Use this skill when the task involves generating a changelog, release notes, or commit summary from a Git repository's history. Suitable for tasks like "generate a changelog for v2.0", "summarize what changed since last release", or "create release notes from git commits". Requires access to a Git repository.

agentscope-ai/agentscope-java · 70 tokens

release-prep

Prepare release documentation including CHANGELOG entry, announcement text, and validation. Run before tagging a new release.

massgen/MassGen · 25 tokens

massgen-release-documenter

Guide for following MassGen's release documentation workflow. This skill should be used when preparing release documentation, updating changelogs, writing case studies, or maintaining project documentation across releases.

massgen/MassGen · 42 tokens

agent-lightning

Provides the action space, tradeoffs, and evaluation context for improving an editable AI agent against a benchmark while preserving its deployment contract. Use when optimizing agent accuracy, cost, latency, or reliability.

microsoft/agent-lightning · 43 tokens

release-notes

Generate user-facing release notes for Intelligent Terminal. Use when asked to write release notes, changelog, what-is-new summary, or prepare a release. Compares git commits between releases, looks up PR-linked issues and community contributors, then outputs formatted notes with "Verbed + Impact + Scenario" style…

microsoft/intelligent-terminal · 73 tokens