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 the-open-agent/oss-skills --skill launch-and-growthgit clone --depth 1 https://github.com/the-open-agent/oss-skillsWrote 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/the-open-agent/oss-skills/launch-and-growth)<a href="https://agentmods.dev/skills/the-open-agent/oss-skills/launch-and-growth"><img src="https://agentmods.dev/badge/skills/the-open-agent/oss-skills/launch-and-growth/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/skills/the-open-agent/oss-skills/launch-and-growth"><img src="https://agentmods.dev/badge/skills/the-open-agent/oss-skills/launch-and-growth.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.00108 | $0.02044 |
| Opus 5 | $0.00054 | $0.01022 |
| Sonnet 5 | $0.00022 | $0.00409 |
| Haiku 4.5 | $0.00011 | $0.00204 |
Grade A, and why
launch-and-growth 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 11d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch and Growth
Distribution is a real problem and ignoring it is not humility. But launches amplify; they do not create. A launch sends a burst of traffic to whatever you have built — if the README is confusing or the install is broken, you have spent your one shot at those people's attention converting them into non-users.
Launch readiness
Do not announce until every one of these is true. Post-launch fixes reach nobody.
[ ] README passes the 30-second test (readme-that-converts)
[ ] Install command verified in a clean container, today
[ ] Quickstart produces a working result in under 5 minutes
[ ] A hero: screenshot, GIF, or a code sample under 10 lines
[ ] LICENSE present and declared in the manifest
[ ] A tagged release exists — not just a main branch
[ ] CI green, badge visible
[ ] Issue templates enabled
[ ] GitHub About: one-liner, link, topics
[ ] Social preview image set (Settings → Social preview)
[ ] You have 4+ uninterrupted hours to answer comments
[ ] Someone other than you has run the quickstart successfully
That last item catches more problems than the rest combined. Watch them do it without helping — every question they ask out loud is a README fix.
Also, honestly: is it ready for strangers? Launching something half-finished burns the audience you will want later. There is no penalty for launching two months late and a real one for launching two months early.
GitHub discoverability
Free, permanent, and consistently neglected:
- Topics — up to 20; use them. This is how GitHub's own search and "explore" surface
you. Include the language, the domain, and the category (
rust,cli,static-analysis,developer-tools). - About — the one-liner and the docs URL. It is what shows in search results.
- Social preview image — controls what appears when your link is shared anywhere. Without it you get a generic gray card, which measurably reduces clicks. Project name + one-liner on a solid background is enough.
- Pinned repos on your profile and org.
- Releases — GitHub surfaces them, and package registries link back.
- A
<name>-awesome-listsubmission in your ecosystem's awesome list — small, durable traffic.
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.
- 11d ago First seen · 160 lines · 108 tokens per session scan A c6d6b2e946a0
launch-and-growth is a skill published in the GitHub repository the-open-agent/oss-skills (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 108 tokens to every session and 2,044 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-31.
Other skills, from other repositories
hyperframes-pr-to-video
Turn a GitHub pull request into a changelog, feature-reveal, fix, or refactor explainer video using HyperFrames. Use when the user provides a PR URL, owner/repo#N ref, or says 'this PR'. Reads diff via gh CLI, visualizes code changes as animated diffs with narration. Teaches diff parsing, change visualization, and…
github-format-standards
Use when the user wants to share a project to GitHub. Runs a full pipeline: root audit, file naming and structure, document fixes (headings, code-block language tags, table alignment, explicit command interpreters), generate missing files (LICENSE, .gitignore, CONTRIBUTING.md, Issue/PR templates), README rewrite…
oss-launch
Use when taking a repo open source, or hardening one that already is. Run /oss-launch and it scans the repo (stack, existing files, git remote, secrets), asks only what it cannot infer, then generates a tailored OSS file collection (README, LICENSE, CONTRIBUTING, CODEOFCONDUCT, SECURITY, CHANGELOG, .gitignore…
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
clawhub-production-release
Run and verify ClawHub production deploys and stable ClawHub CLI npm releases. Use when deploying backend or frontend changes to clawhub.ai, dispatching the Deploy workflow, publishing a stable CLI tag, checking release prerequisites, or proving the exact production SHA and workflow outcome.