competitor-monitoring

competitor-monitoring is a skill for Claude Code from HybridAIOne/hybridclaw. It costs 117 tokens per session (3,124 once invoked), scanned A, original, MIT.

A scheduled competitor-monitoring workflow that compares watched companies with their previous state and reports only changes. It can also monitor industry people when the available sources support it.

In plain words
What is it for?
Use it to add, update, or stop watches, detect company changes, and write concise results to a salesperson's daily note.
Why use it?
It removes the need to check competitors manually and helps avoid filling daily reports with unchanged information.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Good fit Use it to add, update, or stop watches, detect company changes, and write concise results to a salesperson's daily note.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hybridaione/hybridclaw/competitor-monitoring
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 HybridAIOne/hybridclaw --skill competitor-monitoring
Clone the repo
git clone --depth 1 https://github.com/HybridAIOne/hybridclaw

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/hybridaione/hybridclaw/competitor-monitoring"><img src="https://agentmods.dev/badge/skills/hybridaione/hybridclaw/competitor-monitoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 117 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,124 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.00117 $0.03124
Opus 5.5 $0.00047 $0.01250
Sonnet 5.5 $0.00023 $0.00625
Haiku 4.5 $0.00012 $0.00312

Measured 22d ago against content hash 5104a10b15bd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

community-skills/competitor-monitoring/SKILL.md · 260 lines

How it starts

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

Competitor Monitoring

You watch competitors for a salesperson. They read the result in an app, not in the chat — the Sales Companion iOS app parses a fenced watch block from your daily memory note. Your job is not to write a nice report but to detect reliably what changed since the last run, and to leave out everything else.

Keep the tone factual. No "exciting", no "interestingly". A salesperson reads this in twenty seconds in the morning. Write names, titles and details in the user's language.

The four stores

What Where How
Schedule one cron task per target cron add / update / remove — chat only
Watchlist watch/targets.json in the workspace read / write
Comparison state watch/<target-id>.json in the workspace read / write
Result for the app today's daily note memory with action: "append", target: "daily"

watch/targets.json is the watchlist. Scheduled runs cannot call cron at all — the tool is blocked there — so they can only know the full list from this file. Change it in the same step as the cron task, every time:

{"targets": [
  {"id": "<target-id>", "name": "<display name>", "kind": "company",
   "focus": "<what to watch>", "schedule": "<e.g. täglich 07:30>",
   "url": "<website>", "task_id": <number from cron add>}
]}

This and every other <…> shape in this file is a template: fill in real values from the user's request, watch/targets.json or this run. Never write a template, or an example company name from this file, into any file.

task_id is the number cron add reports ("Scheduled … task #42 …"); pass it as taskId to update and remove.

Why these stores: the memory tool may only write today's daily note, and only memory files are synced to the platform, where the app reads them. A workspace file never reaches the app, so it holds your own state.

A. Set up a watch

This happens in a chat with the user, where cron is available.

Read the full file on GitHub · 260 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. 22d ago Changed · +11 lines 5104a10b15bd
  2. 23d ago First seen · 249 lines · 117 tokens per session scan A e3908a5ca5f6

Subscribe to this mod's changes

competitor-monitoring is a skill published in the GitHub repository HybridAIOne/hybridclaw (159 stars, last pushed yesterday), licensed MIT. It adds 117 tokens to every session and 3,124 once invoked, about $0.0005 per session on Opus 5.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-24.