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 skills add hardiktiwari/PM-operating-OS --skill launch-postgit clone --depth 1 https://github.com/hardiktiwari/PM-operating-OSWrote 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/skills/hardiktiwari/pm-operating-os/launch-post)<a href="https://agentmods.dev/skills/hardiktiwari/pm-operating-os/launch-post"><img src="https://agentmods.dev/badge/skills/hardiktiwari/pm-operating-os/launch-post.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.00031 | $0.00462 |
| Opus 5 | $0.00015 | $0.00231 |
| Sonnet 5 | $0.00006 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
launch-post 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.
What it actually says
Launch Post
Help PMs write Slack-native launch announcements. Produces concise, celebratory posts that inform the team what shipped, who it's for, and why it matters.
When to Use
- Shipping a new feature
- Announcing an experiment rollout
- Releasing a product update
- When asked "help me write a launch post for Slack"
- Celebrating a milestone or go-live
Process / Template
1. Gather Key Information
- What shipped — feature name, experiment, or release
- Who it's for — target users or segment
- Key metrics — what success looks like (optional)
- Links — docs, dashboards, Figma, demo
- Kudos — who contributed (optional)
2. Use Slack-Native Format
- Emoji — use sparingly for visual anchor (e.g., 🚀 for launch)
- Short paragraphs — 1–2 sentences max
- Bullets — for scannability
- Links — inline, descriptive (not raw URLs)
- Tone — celebratory but informative
3. Structure the Post
Opening
- One-line hook: what shipped and why it matters
Body
- What — brief description of the change
- Who — target users or segment
- Impact — expected benefit or metric (if known)
- Links — where to learn more, try it, or see data
Closing
- Call to action (try it, give feedback) or kudos
4. Keep It Concise
- Aim for 3–5 short paragraphs or bullet blocks
- Skip internal jargon when possible
- Lead with customer value, not implementation details
Output
A Slack-ready launch post that:
- Fits naturally in a #launches or #shipped channel
- Is scannable in 30 seconds
- Celebrates the team
- Points readers to more detail if they want it
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 · 63 lines · 31 tokens per session scan A 0de598ffaba3
launch-post is a skill published in the GitHub repository hardiktiwari/PM-operating-OS (5 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 462 once invoked, about $0.0002 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.
Other skills, from other repositories
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
firebase-cloud-functions
Use when calling callable functions (httpsCallable), passing data to server-side logic, handling function errors/timeouts, configuring regions, or testing with the Emulator Suite.
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
excalidraw-architect
Choose and compose the right Excalidraw diagram - architecture, flowchart, sequence, state, ER, swimlane, process, timeline, quadrant, pyramid, venn, loop, gantt, bar, line, scatter, and more - using the excalidraw-architect-mcp server. Use whenever a reader would learn more from a picture than from prose, or when…
sdd
Execute the Liatrio Spec-Driven Development (SDD) workflow when explicitly invoked by the user. NOTE: this skill is NOT intended to be dynamically loaded or automatically triggered; it should only ever be explicitly called by the user.
bcc-throughline
BCC global progress cockpit (plans.md/progress.md/findings.md). Slash: /bcc-throughline · chat: bcc:throughline · "where are we" · reprioritize · resume after /clear. Not for coding or full PLAN grill.