A release workflow for preparing tested code and opening a pull request. A pull request is a proposed change for review before it is merged into a project.

Use it to bootstrap a missing test setup, run the project's tests, commit release changes, open a pull request, and update audit records.

It checks for blocked review findings, synchronizes with the main branch, runs tests, and stops when verification fails before code is shipped.

ship — Skill for Claude Code and Codex by rijuvashisht

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.

Any agent

npx skills add rijuvashisht/Magneto --skill ship

Clone the repo

git clone --depth 1 https://github.com/rijuvashisht/Magneto

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/rijuvashisht/magneto/ship/github.svg)](https://agentmods.dev/skills/rijuvashisht/magneto/ship)

Your own site

<a href="https://agentmods.dev/skills/rijuvashisht/magneto/ship"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/ship/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/rijuvashisht/magneto/ship"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 712 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00712
Opus 5	$0.00000	$0.00356
Sonnet 5	$0.00000	$0.00142
Haiku 4.5	$0.00000	$0.00071

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

Security

Grade A, and why

ship 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 10d 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.

src/templates/magneto-skills/skills/ship/SKILL.md · 105 lines

How it starts

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

/ship — Release Engineer: Sync, Test, Bootstrap, PR

Role: Release Engineer Inputs: plan.md, review-report.md (no [BLOCK] findings) Outputs: git commits, opened PR, trace link updates Audit actions: ship.started, ship.tests_bootstrapped, ship.pr_opened

The Protocol

Step 1: Preflight

Check magneto audit verify — fails if audit chain corrupt
Check there are no outstanding [BLOCK] findings in review-report.md
Check /freeze is off (or user explicitly overrides)

Step 2: Sync with main

git fetch origin
git merge origin/main   # or rebase, per project convention

Resolve conflicts if any. If conflicts span unrelated code, STOP and ask.

Step 3: Test bootstrap (if missing)

If the project has no test framework:

Detect stack (package.json → jest/vitest, go.mod → go test, pytest via pyproject.toml, etc.)
Scaffold minimal config + one smoke test
Commit as chore: bootstrap test framework

Emit audit: magneto audit add ship.tests_bootstrapped --payload '{"framework":"..."}'.

Step 4: Run all tests

<project test command>

If any fail, refuse to continue. Cite the failures.

Step 5: Filter-squash WIP commits (gstack pattern)

If continuous checkpoint mode has produced WIP: commits:

git filter-branch --msg-filter '...'   # or interactive rebase

Preserve non-WIP commits. Keep bisect clean.

Step 6: Write trace links (Magneto-unique)

For each changed file, record the design → code link:

magneto trace add --requirement <req-id> --file <path> --test <path>

(Skip if /trace hasn't been initialized.)

Step 7: Generate PR description from sprint artifacts

Pull:

Summary from design.md
File list from plan.md
Findings from review-report.md
Test plan from test-plan.md (if /plan-eng-review ran)

Format:

## Summary
<from design.md>

## Changes
<from plan.md file list>

## Testing
- Tests: <added>/<total> passing
- Coverage: <percent>
<from test-plan.md>

## Review
<summary from review-report.md>

## Trace
<requirement IDs from /trace>

---
Generated by Magneto AI — sprint s-YYYYMMDD-...

Read the full file on GitHub · 105 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.

10d ago First seen · 105 lines · 0 tokens per session scan A db369e57787d

Subscribe to this mod's changes

ship is a skill published in the GitHub repository rijuvashisht/Magneto (6 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 712 tokens. 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.

Git and workflow Releases openai

writing-modpack-changelog

Use when cutting a modpack release. Creates /docs/release-changelog.md if absent; appends a new version section with grouped changes. Triggers - 'cut a release', 'release notes', 'changelog', 'v1.2.3 changes', 'what changed since last version'.

hashgraph-online/awesome-codex-plugins · 69 tokens

multi-repo-release

Prepares and validates GPT-RAG umbrella and multi-repository releases. Use whenever work involves release preparation, semantic versions, release branches, manifest or component pins, changelog release entries, tags, GitHub Release notes, or AI Landing Zone release alignment.

Azure/GPT-RAG · 56 tokens

publish-npm-package

Configure or troubleshoot npm package publication with GitHub Actions and npm Trusted Publishing. Use this skill for JavaScript or TypeScript packages. Also use it for the npm package in a mixed-language repository. Do not use it for applications or repositories without an npm package. Do not use it for generic CI…

btfranklin/skills · 77 tokens

ship