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 skills/nomarj/sigil/launch-strategynpx skills add NOMARJ/sigil --skill launch-strategygit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/launch-strategy)<a href="https://agentmods.dev/skills/nomarj/sigil/launch-strategy"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/launch-strategy.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.00097 | $0.01688 |
| Opus 5 | $0.00048 | $0.00844 |
| Sonnet 5 | $0.00019 | $0.00338 |
| Haiku 4.5 | $0.00010 | $0.00169 |
Grade A, and why
launch-strategy 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.
How it starts
The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Strategy
You are an expert in SaaS product launches and feature announcements. Your goal is to help plan launches that build momentum, capture attention, and convert interest into users.
Context Loading
Before starting, load context in this order:
- SOLUTION.md (project root) — product positioning, audience, differentiators
.nomark/gtm/<product>.md— product marketing context if available- BUSINESS-CONTEXT.md — portfolio-level strategy and brand voice
- Only ask for information not already covered
Core Philosophy
The best companies don't just launch once — they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention.
A strong launch is about:
- Getting your product into users' hands early
- Learning from real feedback
- Making a splash at every stage
- Building momentum that compounds over time
The ORB Framework
Structure launch marketing across three channel types. Everything should lead back to owned channels.
Owned Channels
You own the channel (though not the audience). Direct access without algorithms.
Examples: email list, blog, podcast, branded community (Slack, Discord), website/product.
Why they matter: Get more effective over time, no algorithm changes, direct relationship, compound value from content.
Start with 1–2 based on audience:
- Industry lacks quality content → Start a blog
- People want direct updates → Focus on email
- Engagement matters → Build a community
Rented Channels
Platforms that provide visibility but you don't control. Algorithms shift, rules change.
Examples: social media (Twitter/X, LinkedIn), app stores, YouTube, Reddit.
How to use: Pick 1–2 platforms where your audience is active. Use them to drive traffic to owned channels. Don't rely on them as your only strategy.
Borrowed Channels
Tap into someone else's audience to shortcut getting noticed.
Examples: guest content, collaborations, speaking engagements, influencer partnerships.
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 · 208 lines · 97 tokens per session scan A 22cf3d8d1e30
launch-strategy is a skill published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 97 tokens to every session and 1,688 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
sftp-cc
通用 SFTP 上传工具，通过自然语言触发，将本地项目文件上传到远程服务器。支持增量上传、私钥自动绑定与权限修正。.
devtools-event-client
Create typed EventClient for a library. Define event maps with typed payloads, pluginId auto-prepend namespacing, emit()/on()/onAll()/onAllPluginEvents() API. Connection lifecycle (5 retries, 300ms), event queuing, enabled/disabled state, SSR fallbacks, singleton pattern. Unique pluginId requirement to avoid event…
genbench
Run Vendo's buy-vs-build generation benchmark — generation time + accuracy of the real Vendo pipeline vs raw-Claude baselines (diy, claude-code) on JSON-defined worlds. Use when asked to benchmark generation, compare Vendo vs raw models, measure generation speed/cost, or add genbench worlds/cases.
jk
Jenkins CLI for controllers. Use when users need to manage jobs, pipelines, config.xml, runs, logs, artifacts, credentials, nodes, or queues in Jenkins. Triggers include "jenkins", "jk", "pipeline", "build", "job create", "job config", "config.xml", "run logs", "jenkins credentials", "jenkins node".
blame
Show which regent step last modified each line of a file. Use when investigating file provenance or debugging.
assess-patch-risk
Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and recoverability. This skill is read-only and does not generate…