launch-monitor

launch-monitor is a skill for Claude Code from Nimbleway/agent-skills. It costs 204 tokens per session (5,917 once invoked), scanned A, original, MIT.

A launch-monitoring workflow for tracking press, social media, developer communities, and competitor channels. It follows reactions to a product launch and highlights sentiment, inaccurate descriptions, and competitor responses.

In plain words
What is it for?
Use it to track coverage after an announcement, review audience sentiment, find mischaracterizations, monitor competitor reactions, and decide how to respond.
Why use it?
It brings launch coverage into one ongoing view instead of requiring manual checks across many sites. It helps identify issues that may need a response quickly.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the nimble plugin — 15 skills, 1 command, 2 agents shipped together

Good fit Use it to track coverage after an announcement, review audience sentiment, find mischaracterizations, monitor competitor reactions, and decide how to respond.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nimbleway/agent-skills/launch-monitor
Install

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.

Any agent
npx skills add Nimbleway/agent-skills --skill launch-monitor
Clone the repo
git clone --depth 1 https://github.com/Nimbleway/agent-skills

Made for: Claude Code.

Or install nimble, the plugin that ships this one along with the rest of its 15 skills, 1 command, 2 agents.

Wrote 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.

agentmods badge for launch-monitor

README.md
[![agentmods](https://agentmods.dev/badge/skills/nimbleway/agent-skills/launch-monitor/github.svg)](https://agentmods.dev/skills/nimbleway/agent-skills/launch-monitor)
Your own site
<a href="https://agentmods.dev/skills/nimbleway/agent-skills/launch-monitor"><img src="https://agentmods.dev/badge/skills/nimbleway/agent-skills/launch-monitor/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.

agentmods 80×15 button for launch-monitor

Your own site · 80×15
<a href="https://agentmods.dev/skills/nimbleway/agent-skills/launch-monitor"><img src="https://agentmods.dev/badge/skills/nimbleway/agent-skills/launch-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 204 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,917 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 31
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
  • medium Excessive Agency · line 80
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00204 $0.05917
Opus 5 $0.00102 $0.02959
Sonnet 5 $0.00041 $0.01183
Haiku 4.5 $0.00020 $0.00592

Measured 12d ago against content hash 9d21d7c602fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

launch-monitor 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 12d 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.

skills/launch-monitor/SKILL.md · 491 lines

How it starts

The opening of the file, as written. The whole thing — 491 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Launch Monitor

Monitors press, social, and community forums from launch day — tracking sentiment, flagging mischaracterizations, surfacing competitor responses, and recommending actions so you can respond fast.


Onboarding message

When this skill is triggered for the first time in a session, send this message. Send it exactly once per session, before asking any setup questions. Do not skip it even when the user's opening message already names a product — the onboarding sets expectations for what the skill collects and how it works.

👋 Launch Monitor is ready.

This skill monitors press, social media, developer communities, and competitor channels around a product launch — tracking sentiment, flagging mischaracterizations, surfacing competitor responses, and telling you exactly what to respond to and how.

To start, just say: "Monitor the launch of [product name]"

Or try:

  • "Track coverage since we announced [product] yesterday"
  • "What's the reaction to our [product] launch?"
  • "Flag any mischaracterizations in our [product] press coverage"
  • "How are competitors responding to our [product] launch?"

Would you like me to save your preferences so I skip the questions next time?


Preflight

Follow the transport selection and standard preflight from references/nimble-playbook.md: pick CLI vs MCP at session start, then run the parallel preflight calls (date, profile, memory index) simultaneously. Tag every Nimble CLI call: nimble --client-source nimble-agent-skills <subcommand>.

From the profile (~/.nimble/business-profile.json): load product/brand context and last_runs.launch-monitor for date windowing. Pre-populate setup questions so the user confirms rather than re-enters. If no profile exists, follow the first-run onboarding flow in references/profile-and-onboarding.md and create a stub after the first run.


How to start

Before asking anything, do two quick research steps:

Step A — Resolve alternate names automatically: Search for the product the user named to discover all alternate names, codenames, version names, and related search terms. Do not ask the user for this. Use what you find to build a comprehensive search term list for Step 1.

  • Search: "[product name]" official name OR "also known as" OR codename OR version
  • For Apple products, always check for internal codename, model number, and marketing name variants
  • For software: check GitHub repo names, API names, and SDK names
  • Add all confirmed variants to your search queries silently — the user never needs to see this step

Read the full file on GitHub · 491 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 12d ago First seen · 491 lines · 204 tokens per session scan A 9d21d7c602fd

Subscribe to this mod's changes

launch-monitor is a skill published in the GitHub repository Nimbleway/agent-skills (53 stars, last pushed 16d ago), licensed MIT. It adds 204 tokens to every session and 5,917 once invoked, about $0.0010 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-30.

Related

Other skills, from other repositories

docs

Scale up scraping and drive interactive pages. Use batchscrape for many URLs, getbatchresults to page through async output, scrapewithactions to interact before scraping, and generatellmstxt to produce a site's AI policy file.

mysleekdesigns/crawlforge-mcp · 0 tokens

crawlforge-web-scraping

Scrapes web pages and returns clean Markdown, HTML, plain text, links, or metadata using CrawlForge's scrape, fetchurl, extractcontent, extracttext, extractlinks, extractmetadata, mapsite, and crawldeep tools. Use when the user wants to scrape a URL, fetch a page, get the markdown or text of a website, extract links…

mysleekdesigns/crawlforge-mcp · 134 tokens

crawlforge-change-tracking

Monitors web pages for changes over time with CrawlForge's trackchanges tool. Use when the user wants to track changes to a page, watch a URL, monitor competitor pricing, detect when content updates, get notified of regulation or product-availability changes, or diff a page against a saved baseline. Workflow: create a…

mysleekdesigns/crawlforge-mcp · 105 tokens

crawlforge-deep-research

Runs multi-source web research and autonomous question-answering with CrawlForge's deepresearch, agent, searchweb, and redditsearch tools. Use when the user wants to research a topic, do a deep dive, compare competitors, gather facts with citations, answer a question from the web, search the web, or get a synthesized…

mysleekdesigns/crawlforge-mcp · 154 tokens

crawlforge-getting-started

Orientation and tool-selection guide for the CrawlForge MCP server's 30 web tools. Use when the user is getting started with CrawlForge, asks which CrawlForge tool to use, how to set up the API key, how skills or the CLI work, what a tool costs in credits, or when one tool fails and a fallback is needed. Routes…

mysleekdesigns/crawlforge-mcp · 125 tokens

crawlforge-structured-extraction

Extracts structured JSON and analyzes content with CrawlForge's extractstructured, extractwithllm, extractembeddedstate, scrapestructured, scrapetemplate, processdocument, analyzecontent, summarizecontent, and listollamamodels tools. Use when the user wants to extract specific fields, pull data into a JSON schema…

mysleekdesigns/crawlforge-mcp · 172 tokens