shipping

shipping is a command for Claude Code from zoekdestep/pm-studio. It costs 14 tokens per session (302 once invoked), scanned A, original, MIT.

A command for writing a decision document about whether a product feature should be released. It gathers project context, research, metrics, customer feedback, and rollout information before making a recommendation.

In plain words
What is it for?
Use it to summarize learnings, analyze adoption and other metrics, assess customer sentiment and rollout status, and record success criteria and next steps.
Why use it?
It brings scattered evidence into one document so release decisions are based on results, feedback, and remaining work.

Command for Claude Code

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 commands/zoekdestep/pm-studio/shipping
Clone the repo
git clone --depth 1 https://github.com/zoekdestep/pm-studio

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/zoekdestep/pm-studio/shipping.svg)](https://agentmods.dev/commands/zoekdestep/pm-studio/shipping)
Your own site
<a href="https://agentmods.dev/commands/zoekdestep/pm-studio/shipping"><img src="https://agentmods.dev/badge/commands/zoekdestep/pm-studio/shipping.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 302 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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 $0.00014 $0.00302
Opus 5 $0.00007 $0.00151
Sonnet 5 $0.00003 $0.00060
Haiku 4.5 $0.00001 $0.00030

Measured 4d ago against content hash fd8098bddbea, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

shipping 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 4d 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.

.claude/commands/shipping.md · 40 lines

What it actually says

You are helping write a shipping decision document for: $ARGUMENTS.feature

Follow all instructions in CLAUDE.md (context loading, research, askback, voice, quality checklist, auto-save, agent offering).

WorkIQ Research

Always query WorkIQ for:

  • Related emails, meeting notes, and customer feedback threads
  • Meeting transcripts discussing this feature's rollout
  • Documents and decision records related to this feature

Additional Connectors (if available)

If ~~product analytics is connected:

  • Pull actual metrics for the feature (adoption, engagement, errors, performance)

If ~~user feedback is connected:

  • Pull customer sentiment, support tickets, feature requests related to the feature

If ~~project tracker is connected:

  • Pull rollout status, remaining work items, bugs

Write

Check context/examples/ for shipping decision examples to match structure and voice. Key sections: introduction with current state, learnings (business metrics, customer sentiment, partner learnings), road ahead (recommendation with reasoning, success criteria, future steps).

Auto-save to /output/shipping-decisions/$ARGUMENTS.feature.md.

Agents

After writing, suggest: reviewer, metrics-designer, edge-case-finder, editor.

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. 4d ago First seen · 40 lines · 14 tokens per session scan A fd8098bddbea

Subscribe to this mod's changes

shipping is a command published in the GitHub repository zoekdestep/pm-studio (5 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 302 once invoked, about $0.0001 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-31.