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-playbooknpx skills add NOMARJ/sigil --skill launch-playbookgit 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-playbook)<a href="https://agentmods.dev/skills/nomarj/sigil/launch-playbook"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/launch-playbook.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.00054 | $0.00868 |
| Opus 5 | $0.00027 | $0.00434 |
| Sonnet 5 | $0.00011 | $0.00174 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
launch-playbook 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 5d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Playbook
Pre-requisites
Invoke business-context skill. Read GTM spec for this product.
A launch is a distribution event, not a product event. The product ships when it ships. The launch is when you tell the right people, in the right place, in the right way.
Launch checklist generator
For the target product and motion, produce a checklist in this structure:
T-30 days (pre-launch foundation)
Content and discovery:
- Primary landing page live with clear message and proof point
- AEO-optimised content published (for content-led products)
- GitHub README complete (for developer-led products)
-
llms.txtdeployed at/llms.txt(all products — AI discoverability) -
robots.txtnot blocking AI crawlers - Structured data / schema markup implemented
Outreach preparation:
- ICP list built (for outreach-led launches)
- Warm paths identified (for relationship-led products — never cold)
- Community presence established before asking for anything
Social proof:
- One real proof point documented (number, result, customer quote)
- No fake data, no "beta users said..." without specifics
T-7 days (pre-launch activation)
- Teaser content published (what's coming, why it matters)
- Early access / waitlist open (if applicable)
- Distribution channels primed (community presence, LinkedIn warm-up)
Launch day
Developer-led (Sigil):
- GitHub repo public with complete README
- HN "Show HN" post drafted and ready
- /r/netsec or security Slack communities post ready
- Responsible disclosure paper linked
- One-line install works end-to-end
Content-led (InstaIndex):
- 3+ AEO blog posts live before launch
- Product Hunt submission scheduled
- SEO community posts (Twitter/X, Reddit r/SEO)
- GSC integration docs clear and working
Community-led (PolicyPA):
- Media pitch sent to 3-5 journalists (consumer finance beat)
- Reddit posts in AusFinance, AusLegal — genuine value first
- Product Hunt launch
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.
- 5d ago First seen · 112 lines · 54 tokens per session scan A ab75dcb97fdc
launch-playbook is a skill published in the GitHub repository NOMARJ/sigil (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 54 tokens to every session and 868 once invoked, about $0.0003 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 上传工具，通过自然语言触发，将本地项目文件上传到远程服务器。支持增量上传、私钥自动绑定与权限修正。.
regex-mastery
Use this skill when writing regular expressions, debugging pattern matching,optimizing regex performance, or implementing text validation. Triggers on regex, regular expressions, pattern matching, lookahead, lookbehind, named groups, capture groups, backreferences, and any task requiring text pattern matching.
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…
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".
t0-orchestrator
Master orchestration for the VNX multi-terminal system. Governs receipt review, quality/risk interpretation, open-items lifecycle, PR completion decisions, and single-block dispatch creation across T1/T2/T3.
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…