shipping-methodology

shipping-methodology is a skill for Claude Code from povvo/claudikins-kernel. It costs 51 tokens per session (3,167 once invoked), scanned A, original, MIT.

A release workflow for preparing code changes, pull requests, changelogs, and merges. It uses review checkpoints and requires a person to approve the final merge.

In plain words
What is it for?
Use it before releasing changes, writing release notes, preparing pull requests, choosing between combining or preserving commits, and checking failed builds.
Why use it?
It reduces the risk of shipping code that was not verified or changed after verification. It also gives a clear process for handling CI failures and merge conflicts.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the claudikins-kernel plugin — 4 skills, 4 commands, 7 agents, 8 hooks shipped together

Good fit Use it before releasing changes, writing release notes, preparing pull requests, choosing between combining or preserving commits, and checking failed builds.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/povvo/claudikins-kernel/shipping-methodology
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 povvo/claudikins-kernel --skill shipping-methodology
Clone the repo
git clone --depth 1 https://github.com/povvo/claudikins-kernel

Made for: Claude Code.

Or install claudikins-kernel, the plugin that ships this one along with the rest of its 4 skills, 4 commands, 7 agents, 8 hooks.

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 shipping-methodology

README.md
[![agentmods](https://agentmods.dev/badge/skills/povvo/claudikins-kernel/shipping-methodology/github.svg)](https://agentmods.dev/skills/povvo/claudikins-kernel/shipping-methodology)
Your own site
<a href="https://agentmods.dev/skills/povvo/claudikins-kernel/shipping-methodology"><img src="https://agentmods.dev/badge/skills/povvo/claudikins-kernel/shipping-methodology/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.

agentmods 80×15 button for shipping-methodology

Your own site · 80×15
<a href="https://agentmods.dev/skills/povvo/claudikins-kernel/shipping-methodology"><img src="https://agentmods.dev/badge/skills/povvo/claudikins-kernel/shipping-methodology.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,167 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.03167
Opus 5.5 $0.00020 $0.01267
Sonnet 5.5 $0.00010 $0.00633
Haiku 4.5 $0.00005 $0.00317

Measured 2mo ago against content hash e7df68b97ef6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

shipping-methodology scanned grade A 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| Evidence summary | Screenshots, curl responses from catastrophiser |
skills/shipping-methodology/SKILL.md · 526 lines

How it starts

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

Shipping Methodology

When to use this skill

Use this skill when you need to:

  • Run the claudikins-kernel:ship command
  • Prepare commit messages and PR descriptions
  • Update changelogs and documentation
  • Decide merge strategy (squash vs preserve)
  • Handle CI failures or merge conflicts
  • Validate code integrity before shipping

Core Philosophy

"Ship with confidence, not hope." - Shipping philosophy

Shipping is the final gate. Apply GRFP-style iterative workflow to every stage.

The Five Principles

  1. Gate check first - claudikins-kernel:verify must have passed. No exceptions.
  2. Code integrity - Ship exactly what was verified. No sneaky changes.
  3. GRFP everywhere - Section-by-section approval at every stage.
  4. Human decides - No auto-merging. Human approves final merge.
  5. Clean up after - Delete branches, update docs, celebrate.

The Five Stages

Stage 1: Pre-Ship Review

Show what's being shipped. Human confirms ready.

Check What to Show
Verification status All phases PASS from claudikins-kernel:verify
Branches to merge List all execute/task-* branches
Evidence summary Screenshots, curl responses from catastrophiser
Code delta Lines added/removed, files changed

Checkpoint:

Ready to ship?

Verified: ✓ All checks passed
Branches: 3 branches to merge
Changes: +450 / -120 lines

[Continue] [Back to Verify] [Abort]

Stage 2: Commit Strategy

Draft commit message(s). Human approves.

Decision:

How should we commit?

[Squash into single commit] [Preserve commit history]

Squash (recommended for features):

  • Single clean commit on main
  • Clear feature boundary
  • Easier to revert if needed

Preserve (for large multi-part work):

  • Keeps granular history
  • Better for debugging
  • Use for multi-feature batches

Read the full file on GitHub · 526 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. 2mo ago First seen · 526 lines · 51 tokens per session scan A e7df68b97ef6

Subscribe to this mod's changes

shipping-methodology is a skill published in the GitHub repository povvo/claudikins-kernel (127 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 3,167 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

shipping-methodology compared with skills from other repositories

shipping-methodology next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
shipping-methodologypovvo/claudikins-kernelSkill1276mo agoMITA51Claude Code
codex-changelogzeikar/hyperclaudeSkill523d agoMITA129Claude Code
git-workflowRealDougEubanks/ClaudeMarketplaceSkill17d agoMITA34Claude Code
changelog-generatorRealDougEubanks/ClaudeMarketplaceSkill17d agoMITA37Claude Code
agent-based-developmentRealDougEubanks/ClaudeMarketplaceSkill17d agoMITA34Claude Code
abd-devopsRealDougEubanks/ClaudeMarketplaceSkill17d agoMITA30Claude Code
releasenarlei/claudecodenotifySkill104mo agoMITA147Claude Code