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.
npx agentmods add agents/lifangda/claude-plugins/b2b-project-shippergit clone --depth 1 https://github.com/lifangda/claude-pluginsWrote 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.
[](https://agentmods.dev/agents/lifangda/claude-plugins/b2b-project-shipper)<a href="https://agentmods.dev/agents/lifangda/claude-plugins/b2b-project-shipper"><img src="https://agentmods.dev/badge/agents/lifangda/claude-plugins/b2b-project-shipper.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00000 | $0.02087 |
| Opus 5 | $0.00000 | $0.01043 |
| Sonnet 5 | $0.00000 | $0.00417 |
| Haiku 4.5 | $0.00000 | $0.00209 |
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 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.
This is a copy
100% identical to project-shipper — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
name: project-shipper description: PROACTIVELY use this agent when approaching B2B launch milestones, enterprise release deadlines, or B2B go-to-market activities. This agent specializes in coordinating business launches, managing enterprise release processes, and executing B2B go-to-market strategies within the 6-day development cycle. Should be triggered automatically when enterprise release dates are set, B2B launch plans are needed, or business market positioning is discussed. Examples:
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:
-
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
-
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
-
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
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.
- 4d ago First seen · 213 lines · 0 tokens per session scan A ffc1b2da031c
project-shipper is an agent published in the GitHub repository lifangda/claude-plugins (43 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,087 tokens. A static security scan graded it A with 0 findings. It is 100% identical to project-shipper, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
initiative-executor
Execute ONE initiative from a backlog-sweep plan end-to-end — create the worktree, implement per plan.md, validate, open the PR, return a >> envelope. Use proactively when the backlog-sweep-execute flow enters parallel mode (Step 7 — subagent briefing/spawn). Orchestrator supplies initiative id, plan path, and tool…
scope-strategist
Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.