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.
git clone --depth 1 https://github.com/zhou210712/claude-for-legal-ZHWrote 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/agents/zhou210712/claude-for-legal-zh/launch-watcher)<a href="https://agentmods.dev/agents/zhou210712/claude-for-legal-zh/launch-watcher"><img src="https://agentmods.dev/badge/agents/zhou210712/claude-for-legal-zh/launch-watcher/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/agents/zhou210712/claude-for-legal-zh/launch-watcher"><img src="https://agentmods.dev/badge/agents/zhou210712/claude-for-legal-zh/launch-watcher.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.00058 | $0.00953 |
| Opus 5.5 | $0.00023 | $0.00381 |
| Sonnet 5.5 | $0.00012 | $0.00191 |
| Haiku 4.5 | $0.00006 | $0.00095 |
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 1mo 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.
This is a copy
100% identical to launch-watcher — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Watcher Agent
Purpose
Product counsel gets blindsided when a launch shows up two days before ship date with no legal review. This agent watches the launch tracker and surfaces what's coming — filtered for things that actually need a look, per the 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
- Read
~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md→ launch tracker location, calibration table, escalation channel. - Query the tracker for tickets with a target date ≤30 days out.
- For each, run a lightweight version of
is-this-a-problemagainst the ticket title/description. - Filter: only surface tickets that match "usually requires work" or "usually blocks" patterns, or that mention trigger keywords.
- Post the filtered list to the channel.
Trigger keywords
Beyond calibration patterns, also flag tickets mentioning:
Privacy triggers:
- "new data" / "collect" / "tracking"
- "under 13" / "children" / "COPPA" — triggers children's privacy review
- "teen" / "minor" / "13-17" / "age-appropriate" / "student" — triggers teen / age-appropriate-design review (different regime, different calibration)
- "health" / "medical" / "HIPAA"
- "personal data" / "PII" / "user data"
- Third-party vendor names not on the approved list
- "terms" / "policy" / "agreement" changes
- Country names (jurisdictional expansion)
- "beta" → "GA" transitions (commitments change)
AI governance triggers:
- "AI" / "ML" / "model" / "LLM" / "GPT" / "Claude" / "Gemini" / "Copilot"
- "machine learning" / "neural" / "algorithm"
- "automated" / "auto-" (when combined with decision or action)
- "generated" / "generative" / "synthesized"
- "recommendation" / "prediction" / "scoring" / "classification"
- "personalized" / "intelligent" (feature descriptions)
- AI vendor names: "OpenAI" / "Anthropic" / "Google AI" / "Cohere" / "Mistral" or similar
- "fine-tun" / "train" / "embeddings"
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.
- 1mo ago First seen · 83 lines · 58 tokens per session scan A 48f64b904655
launch-watcher is an agent published in the GitHub repository zhou210712/claude-for-legal-ZH (238 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 953 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to launch-watcher, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
ip-renewal-watcher
Scheduled agent that reads the IP portfolio register, computes what's due, and posts a ranked deadline report. Runs weekly by default. Posts to the channel named in /.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md → Renewal alerts. Trigger phrases: "what's renewing", "IP deadlines", "portfolio check", "IP…
launch-watcher
Monitors the launch tracker (Jira/Linear) for upcoming launches that likely need legal review, flags them before product counsel gets surprised. Runs daily. Trigger: "what launches are coming", "what should I know about", "launch radar", or on schedule.
reg-change-monitor
Scheduled agent that checks regulatory feeds and posts a filtered digest. Runs per the cadence in /.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md. Filters by materiality threshold so the digest is signal, not noise. Trigger: "reg digest", "what's new from regulators", or on schedule.
keel
Designs processes, SOPs, OKR cascades, vendor contracts, and compliance programs that scale with company growth. Use when documenting a business process, auditing ops posture, or managing vendor contracts. Trigger with "write a SOP", "build our OKR framework".
Recruitment Specialist
Expert recruitment operations and talent acquisition specialist — skilled in China's major hiring platforms, talent assessment frameworks, and labor law compliance. Helps companies efficiently attract, screen, and retain top talent while building a competitive employer brand.
managing-partner
Runs the AI law firm. Receives each legal matter, consults Jurisdiction Counsel, assigns a Specialist Lawyer as Matter Owner, dispatches delegation requests, reviews the consolidated work and delivers one verified work product.