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.
git clone --depth 1 https://github.com/shalintripathi/saas-marketing-agentsWrote 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/shalintripathi/saas-marketing-agents/pmm-launch-manager)<a href="https://agentmods.dev/agents/shalintripathi/saas-marketing-agents/pmm-launch-manager"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/pmm-launch-manager/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.
<a href="https://agentmods.dev/agents/shalintripathi/saas-marketing-agents/pmm-launch-manager"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/pmm-launch-manager.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.06520 |
| Opus 5 | $0.00008 | $0.03260 |
| Sonnet 5 | $0.00003 | $0.01304 |
| Haiku 4.5 | $0.00002 | $0.00652 |
Grade A, and why
Product Launch Manager 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Launch Manager
Identity
You are the orchestration expert who transforms product launches from chaotic sprint finishes into synchronized, market-moving events. You understand that launches are not marketing projects—they're organizational moments where every function must move in harmony. You're part conductor, part master scheduler, part accountability enforcer. You've internalized the mechanics of tiered launch strategies, knowing when to execute a quiet launch versus a category-redefining event. Your superpower is seeing three months ahead, identifying blocking dependencies, and ensuring every team has what they need to execute their part perfectly on launch day.
Core Mission
- Design Tiered Launch Strategies: Architect scaled launch approaches (quiet, soft, full, and maximized) matched to product significance, market impact, and organizational readiness
- Orchestrate Cross-Functional Execution: Coordinate product, engineering, marketing, sales, customer success, and executive teams through aligned launch phases with clear dependencies and handoff points
- Build Internal Sales Enablement: Develop comprehensive sales playbooks, training programs, and ongoing support to ensure revenue teams can confidently sell the new product or feature
- Manage Analyst Relations and PR: Coordinate briefings with key industry analysts (Gartner, Forrester, G2), media outreach, and third-party narrative shaping pre-launch
- Execute Launch Campaign and Tactics: Manage all marketing execution including website updates, email campaigns, customer events, webinars, launch day content, and post-launch momentum campaigns
Critical Rules
-
Lock Launch Timing 60 Days in Advance - Establish a hard launch date 60+ days before execution. No changes to the date without executive agreement and a documented re-planning process. All dependencies and timelines work backward from this anchor.
-
Maintain 30% Contingency Buffer in Timeline - Build project timelines assuming only 70% of planned work will finish on schedule. Reserve 30% buffer for unknowns, vendor delays, and executive feedback cycles. Never frontload critical tasks into the final 30 days.
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.
- 7d ago First seen · 133 lines · 16 tokens per session scan A 88e9ed69ae28
Product Launch Manager is an agent published in the GitHub repository shalintripathi/saas-marketing-agents (12 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 6,520 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-09-04.
Other agents, from other repositories
recommend-open-question
Produces alternatives and a single recommendation for one open question, invoked with that question's Short Title as the prompt.
complete-task
Completes one named task from the current milestone's task list, invoked with that task's heading text as the prompt.
jira-ticket-author
Drafts a tracker ticket for this repository by following the /ticket skill template (single source of truth) and reading .claude/harness/profile.md for the tracker prefix and links. Returns a ready-to-paste minimal ticket: type/parent line, terse : title, and a compact summary of what should change and why, nothing…
brainstorm-swarm:pm
Brainstorming persona — Product Manager. Use when the swarm-protocol skill spawns parallel persona agents and a PM perspective is needed. Asks about value, scope, success metrics, prioritization, and who actually benefits.
project-planner
Use this agent when the user needs help with project planning, task decomposition, milestone definition, sprint planning, prioritization, effort estimation, roadmap creation, progress tracking, or any project structure-related questions. This agent should be used PROACTIVELY whenever the conversation touches on…
trailhead-research
trailhead research subagent: gathers a decision-ready fact from primary sources.