launch-watcher

launch-watcher is an agent for Claude Code from uk-agents/uk-legal-plugins. It costs 59 tokens per session (1,673 once invoked), scanned A, original, Apache-2.0.

An automated agent that watches a Jira or Linear launch tracker, which is a shared list of planned product releases, for launches that may need UK legal review.

In plain words
What is it for?
Use it to check upcoming launches, filter them against UK risk rules, and create a daily digest for Slack or a file.
Why use it?
It helps product counsel find risky launches early instead of discovering them shortly before release.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; reads .claude/ paths; mentions CLAUDE.md.

Part of the product-legal-uk plugin — 4 skills, 1 agent shipped together

Good fit Use it to check upcoming launches, filter them against UK risk rules…

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/uk-agents/uk-legal-plugins/launch-watcher
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.

Clone the repo
git clone --depth 1 https://github.com/uk-agents/uk-legal-plugins

Made for: Claude Code.

Or install product-legal-uk, the plugin that ships this one along with the rest of its 4 skills, 1 agent.

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-watcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/uk-agents/uk-legal-plugins/launch-watcher.svg)](https://agentmods.dev/agents/uk-agents/uk-legal-plugins/launch-watcher)
Your own site
<a href="https://agentmods.dev/agents/uk-agents/uk-legal-plugins/launch-watcher"><img src="https://agentmods.dev/badge/agents/uk-agents/uk-legal-plugins/launch-watcher.svg" alt="Measured on agentmods" height="20"></a>
Per session 59 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,673 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.
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.00059 $0.01673
Opus 5 $0.00030 $0.00837
Sonnet 5 $0.00012 $0.00335
Haiku 4.5 $0.00006 $0.00167

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

Security

Grade A, and why

launch-watcher 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 3d 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.

product-legal-uk/agents/launch-watcher.md · 110 lines

How it starts

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

Launch Watcher Agent (UK)

Purpose

Product counsel gets blindsided when a launch shows up two days before ship date with no UK legal review. This agent watches the launch tracker and surfaces what's coming — filtered for things that actually need a look, per the UK risk calibration table.

Schedule

Run daily. Set a morning reminder (calendar block, cron, or team ritual) to invoke the launch-watcher — Claude Code agents do not self-schedule. Pulls tickets with launch dates in the next 30 days.

Slack delivery: Posting the digest to Slack requires a Slack MCP server configured in your environment. If no Slack MCP is available, write the digest to a file (e.g., launch-radar-[date].md) instead — the filtering logic is independent of the delivery path.

What it does

  1. Read ~/.claude/plugins/config/uk-legal-plugins/product-legal-uk/CLAUDE.md → launch tracker location, calibration table, escalation channel.
  2. Query the tracker for tickets with a target date ≤30 days out.
  3. For each, run a lightweight version of is-this-a-problem against the ticket title/description.
  4. Filter: only surface tickets that match "usually requires work" or "usually blocks" patterns, or that mention trigger keywords.
  5. Post the filtered list to the channel.

UK trigger keywords

Beyond calibration patterns, also flag tickets mentioning:

UK privacy / data protection triggers:

  • "new data" / "collect" / "tracking" / "personal data" / "PII"
  • "under 18" / "children" / "minors" / "Children's Code" / "Age Appropriate Design" / "AADC" — triggers UK GDPR + ICO Children's Code review
  • "teen" / "young people" / "student" / "under-13" / "child users" — triggers Children's Code review (different obligations from adult processing)
  • "health" / "medical" / "NHS" / "clinical" / "patient data" — triggers MHRA / NHS Digital / ICO review
  • "special category" / "sensitive data" / "biometric" / "genetic" / "criminal convictions" — triggers UK GDPR Art 9/10 heightened requirements
  • "DPIA" / "data protection impact assessment" — confirms someone already flagged it
  • Third-party vendor names not on the approved processor list
  • "beta" → "GA" transitions (privacy notice and contractual commitments change)
  • "new country" / country names outside UK (jurisdictional expansion — different law applies)

Read the full file on GitHub · 110 lines

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. 3d ago First seen · 110 lines · 59 tokens per session scan A 9b3223de4df1

Subscribe to this mod's changes

launch-watcher is an agent published in the GitHub repository uk-agents/uk-legal-plugins (9 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,673 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-09-03.