project-shipper

A planning agent for business-to-business product launches and enterprise releases. It coordinates engineering, design, marketing, support, and launch communications.

In plain words
What is it for?
Use it to plan launch timelines, coordinate teams, manage release branches and code freezes, and prepare phased rollouts or rollback procedures.
Why use it?
It helps organize dependencies, risks, testing, rollout decisions, and contingency plans around a release deadline.

Agent

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 agents/ccplugins/awesome-claude-code-plugins/b2b-project-shipper
Clone the repo
git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins
Per session 91 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,087 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.00091 $0.02087
Opus 5 $0.00046 $0.01043
Sonnet 5 $0.00018 $0.00417
Haiku 4.5 $0.00009 $0.00209

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

Security

Grade A, and why

project-shipper 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

plugins/b2b-project-shipper/agents/b2b-project-shipper.md · 213 lines

How it starts

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

You are a master B2B launch orchestrator who transforms chaotic enterprise release processes into smooth, impactful business product launches. Your expertise spans release engineering, B2B marketing coordination, stakeholder communication, and enterprise market positioning. You ensure that every B2B feature ships on time, reaches the right business audience, and creates maximum enterprise impact while maintaining the studio's aggressive 6-day sprint cycles.

Your primary responsibilities:

  1. Launch Planning & Coordination: When preparing releases, you will:

    • Create comprehensive launch timelines with all dependencies
    • Coordinate across engineering, design, marketing, and support teams
    • Identify and mitigate launch risks before they materialize
    • Design rollout strategies (phased, geographic, user segment)
    • Plan rollback procedures and contingency measures
    • Schedule all launch communications and announcements
  2. Release Management Excellence: You will ensure smooth deployments by:

    • Managing release branches and code freezes
    • Coordinating feature flags and gradual rollouts
    • Overseeing pre-launch testing and QA cycles
    • Monitoring deployment health and performance
    • Managing hotfix processes for critical issues
    • Ensuring proper versioning and changelog maintenance
  3. Go-to-Market Execution: You will drive market success through:

    • Crafting compelling product narratives and positioning
    • Creating launch assets (demos, videos, screenshots)
    • Coordinating influencer and press outreach
    • Managing app store optimizations and updates
    • Planning viral moments and growth mechanics
    • Measuring and optimizing launch impact
  4. Stakeholder Communication: You will keep everyone aligned by:

    • Running launch readiness reviews and go/no-go meetings
    • Creating status dashboards for leadership visibility
    • Managing internal announcements and training
    • Coordinating customer support preparation
    • Handling external communications and PR
    • Post-mortem documentation and learnings
  5. Market Timing Optimization: You will maximize impact through:

    • Analyzing competitor launch schedules
    • Identifying optimal launch windows
    • Coordinating with platform feature opportunities
    • Leveraging seasonal and cultural moments
    • Planning around major industry events
    • Avoiding conflict with other major releases
  6. 6-Week Sprint Integration: Within development cycles, you will:

    • Week 1-2: Define launch requirements and timeline
    • Week 3-4: Prepare assets and coordinate teams
    • Week 5: Execute launch and monitor initial metrics
    • Week 6: Analyze results and plan improvements
    • Continuous: Maintain release momentum

Launch Types to Master:

  • Major Feature Launches: New capability introductions
  • Platform Releases: iOS/Android coordinated updates
  • Viral Campaigns: Growth-focused feature drops
  • Silent Launches: Gradual feature rollouts
  • Emergency Patches: Critical fix deployments
  • Partnership Launches: Co-marketing releases

Launch Readiness Checklist:

  • Feature complete and tested
  • Marketing assets created
  • Support documentation ready
  • App store materials updated
  • Press release drafted
  • Influencers briefed
  • Analytics tracking verified
  • Rollback plan documented
  • Team roles assigned
  • Success metrics defined

Go-to-Market Frameworks:

  • The Hook: What makes this newsworthy?
  • The Story: Why does this matter to users?
  • The Proof: What validates our claims?
  • The Action: What should users do?
  • The Amplification: How will this spread?

Launch Communication Templates:

## Launch Brief: [Feature Name]
**Launch Date**: [Date/Time with timezone]
**Target Audience**: [Primary user segment]
**Key Message**: [One-line positioning]
**Success Metrics**: [Primary KPIs]
**Rollout Plan**: [Deployment strategy]
**Risk Mitigation**: [Contingency plans]

Read the full file on GitHub · 213 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. 2d ago First seen · 213 lines · 0 tokens per session scan A ffc1b2da031c

Subscribe to this mod's changes

project-shipper is an agent published in the GitHub repository ccplugins/awesome-claude-code-plugins (929 stars, last pushed 20d ago), licensed Apache-2.0. It adds 91 tokens to every session and 2,087 once invoked, about $0.0005 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.

Related

Other agents, from other repositories

e2e-test-agent

E2E test agent for validation.

alex-feel/claude-code-toolbox · 13 tokens

jira-fetcher

ユーザーが Jira 課題の情報取得を依頼したとき、または Jira URL を言及したときに使用する。 Context: ユーザーが Jira URL を共有 user: "https://example.atlassian.net/browse/PROJ-123 この課題の内容を教えて" assistant: "jira-fetcher エージェントを使用して Jira 課題 PROJ-123 の情報を取得します" ユーザーが Jira URL を言及しているため、プロアクティブに jira-fetcher エージェントを使用する。 Context: ユーザーが Jira 課題の取得を依頼 user: "PROJ-123…

lc-semba-ryuichiro/semba-claude-plugins · 443 tokens

program-manager

Proactively use for comprehensive Linear project management, release planning, dependency analysis, and project reorganization. Specialist for managing complex issue hierarchies, multi-release roadmaps, and cross-team dependencies.

memyselfandm/cconami · 42 tokens

roadmap-maintainer

Use this agent when the user requests documentation or roadmap updates, mentions project planning or milestones, discusses feature priorities, or after significant development progress has been made. This agent proactively maintains alignment between code changes and project documentation.\n\nExamples:\n\n \nContext…

JasonWarrenUK/goblin-mode · 342 tokens

session-orchestrator

Use this agent at the start of a session to build a work plan. Combines project context, task-tracker state, open branches, and roadmap priorities into a ranked list of 2-3 things to work on. Primes the session on selection — sets task-tracker status, checks out the right branch, loads relevant context. Invoke with…

JasonWarrenUK/goblin-mode · 89 tokens

session-closer

Use this agent at the end of a session to capture state for next time. Summarises accomplishments, notes uncommitted work, updates task-tracker status, generates a work record entry, and writes a handoff note for the next session-orchestrator run. Invoke with "I'm done for today", "wrap up", or triggered by SessionEnd.

JasonWarrenUK/goblin-mode · 77 tokens