product-os: Command for Claude Code

.claude/commands/competitor-monitor.md

competitor-monitor is a command for Claude Code from motorway-sandbox/product-os. It costs 0 tokens per session (959 once invoked), scanned A, original, MIT.

An on-demand competitor-monitoring command that searches for recent competitor and market news.

In plain words
What is it for?
It is for searching the web, assessing the importance of findings, and presenting a summary for direction.
Why use it?
It gathers scattered updates into a review of product launches, funding, leadership changes, market shifts, and relevant regulation.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is motorway-sandbox/product-os's own configuration. It tells Claude Code how to work on product-os itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything product-os configures →

Reuse

Borrowing it

Nothing to install: this file belongs to motorway-sandbox/product-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/motorway-sandbox/product-os/main/.claude/commands/competitor-monitor.md
Clone the repo
git clone --depth 1 https://github.com/motorway-sandbox/product-os

Made for: Claude Code.

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 competitor-monitor

README.md
[![agentmods](https://agentmods.dev/badge/commands/motorway-sandbox/product-os/competitor-monitor/github.svg)](https://agentmods.dev/commands/motorway-sandbox/product-os/competitor-monitor)
Your own site
<a href="https://agentmods.dev/commands/motorway-sandbox/product-os/competitor-monitor"><img src="https://agentmods.dev/badge/commands/motorway-sandbox/product-os/competitor-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 competitor-monitor

Your own site · 80×15
<a href="https://agentmods.dev/commands/motorway-sandbox/product-os/competitor-monitor"><img src="https://agentmods.dev/badge/commands/motorway-sandbox/product-os/competitor-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 959 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.00000 $0.00959
Opus 5 $0.00000 $0.00479
Sonnet 5 $0.00000 $0.00192
Haiku 4.5 $0.00000 $0.00096

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

Security

Grade A, and why

competitor-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 7d 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.

.claude/commands/competitor-monitor.md · 91 lines

How it starts

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

You are running an on-demand competitor monitor. This is an interactive session — present findings and ask for direction.

Task

Search the web for competitor and market news relevant to {Your Company}, save structured results, and present a summary.

Run the following 9 web searches (run as many in parallel as possible):

Competitor-specific:

  1. "{Competitor 1}" news — last 7 days
  2. "{Competitor 2}" news — last 7 days
  3. "{Competitor 3}" news — last 7 days
  4. "{Competitor 4}" news — last 7 days

Thematic: 5. {your industry} market trends — last 7 days 6. {your industry} AI startups — last 7 days 7. {your industry} funding OR investment — last 7 days

For each search, review the top results. Use WebFetch to read any articles that look significant (new product launches, funding rounds, executive changes, market shifts, regulatory changes, technology moves).

Step 2: Evaluate

For each piece of news found, assess:

  • Significance: High / Medium / Low
    • High: direct competitive threat, major funding/M&A, product launch that overlaps with {Your Company}, regulatory change affecting the market
    • Medium: notable but indirect — market trend, executive hire, geographic expansion
    • Low: routine coverage, minor updates, no clear implication for {Your Company}
  • {Your Company} implication: 1–2 sentences on what this means for {Your Company}'s strategy, positioning, or priorities

Discard Low-significance items unless 3+ Low items together suggest a pattern worth noting.

Step 3: Check for duplicates

Read the existing per-competitor tracking files to avoid repeating news already logged:

  • insights/market/competitors/{competitor-1}.md
  • insights/market/competitors/{competitor-2}.md
  • insights/market/competitors/{competitor-3}.md

Read the full file on GitHub · 91 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. 7d ago First seen · 91 lines · 0 tokens per session scan A fc5a1e914dc6

Subscribe to this mod's changes

competitor-monitor is a command published in the GitHub repository motorway-sandbox/product-os (10 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 959 tokens. 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-04.