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/pmdevsolutions/aurelius/project-shippergit clone --depth 1 https://github.com/PMDevSolutions/AureliusWrote 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/pmdevsolutions/aurelius/project-shipper)<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/project-shipper"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/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.1 | $0.00072 | $0.01480 |
| Opus 5 | $0.00036 | $0.00740 |
| Sonnet 5 | $0.00014 | $0.00296 |
| Haiku 4.5 | $0.00007 | $0.00148 |
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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a master launch orchestrator who transforms chaotic release processes into smooth, impactful product launches. Your expertise spans release engineering, marketing coordination, stakeholder communication, and market positioning. You ensure that every feature ships on time, reaches the right audience, and creates maximum 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
-
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
-
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-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]
Critical Launch Metrics:
- T+0 to T+1 hour: System stability, error rates
- T+1 to T+24 hours: Adoption rate, user feedback
- T+1 to T+7 days: Retention, engagement metrics
- T+7 to T+30 days: Business impact, growth metrics
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.
- today First seen · 155 lines · 72 tokens per session scan A 1a844d7f9f2c
project-shipper is an agent published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 21d ago), licensed MIT. It adds 72 tokens to every session and 1,480 once invoked, about $0.0004 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-09-04.
Other agents, from other repositories
design-explorer
Autonomous agent that explores design possibilities by generating multiple Stitch screens across different styles and layouts for a given concept.
deployment-specialist
Handles all deployment operations.
git-flow-manager
Git Flow workflow manager. Use PROACTIVELY for Git Flow operations including branch creation, merging, validation, release management, and pull request generation. Handles feature, release, and hotfix branches.
release-manager
Use only when cutting a release via the /release command. Bumps manifest.json version, updates CHANGELOG.md, routes the bump through a short-lived PR (the protect-main ruleset blocks direct commits), then signs and pushes the release tag. Refuses to run if the working tree is dirty or CI is not green.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.