agentmods.dev

radar-diff-changes

radar-diff-changes is a skill for Claude Code from sabahudin-web/competitive-intelligence-radar. It costs 75 tokens per session (543 once invoked), scanned A, original, MIT.

A comparison step for competitor research that checks the latest competitor reports against the previous run and lists meaningful changes.

In plain words
What is it for?
It helps track search-ranking moves, price changes, new headlines, sentiment shifts, and new or missing competitors between research runs.
Why use it?
It prevents teams from treating old or stale information as a new development. It also ranks the changes so important movements are easier to find.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the competitive-intelligence-radar plugin — 8 skills, 3 commands, 5 agents, 2 MCP servers shipped together

not rated 3 2mo ago A scan 75 tokens original MIT
View the source file sabahudin-web/competitive-intelligence-radar linkedin.com
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.

agentmods
npx agentmods add skills/sabahudin-web/competitive-intelligence-radar/radar-diff-changes
Any agent
npx skills add sabahudin-web/competitive-intelligence-radar --skill radar-diff-changes
Clone the repo
git clone --depth 1 https://github.com/sabahudin-web/competitive-intelligence-radar

Made for: Claude Code.

Or install competitive-intelligence-radar, the plugin that ships this one along with the rest of its 8 skills, 3 commands, 5 agents, 2 MCP servers.

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 radar-diff-changes

README.md
[![agentmods](https://agentmods.dev/badge/skills/sabahudin-web/competitive-intelligence-radar/radar-diff-changes.svg)](https://agentmods.dev/skills/sabahudin-web/competitive-intelligence-radar/radar-diff-changes)
Your own site
<a href="https://agentmods.dev/skills/sabahudin-web/competitive-intelligence-radar/radar-diff-changes"><img src="https://agentmods.dev/badge/skills/sabahudin-web/competitive-intelligence-radar/radar-diff-changes.svg" alt="Measured on agentmods" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 543 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00075 $0.00543
Opus 5 $0.00037 $0.00271
Sonnet 5 $0.00015 $0.00109
Haiku 4.5 $0.00007 $0.00054

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

Security

Grade A, and why

radar-diff-changes 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 5d 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/radar-diff-changes/SKILL.md · 46 lines

What it actually says

radar-diff-changes

Automation level: AUTONOMOUS.

Goal: compute an honest, freshness-aware change set between the current run and the last one.

Steps

  1. Read radar.config.json to find last_run.dossier_dir (the previous run) and the current run directory from the caller. If there is no previous run, this is the baseline: every competitor is marked New and there are no deltas to compute. Say so.

  2. Load all dossier JSON files from both runs, matched by competitor domain (the stable key).

  3. For each competitor and each field, compare ONLY when the field is within its recency window on BOTH runs (see freshness.md). A comparison across a stale value is not a real change; skip it and note the field as "not comparable this run."

  4. Classify each material change with a type the dashboard understands:

    • RISING: competitor improved SERP rank, gained funding, ramped hiring, sentiment up.
    • FALLING: competitor lost rank, negative news, sentiment down.
    • PRICE: pricing or packaging changed.
    • NEWS: a fresh in-window headline that did not exist last run.
    • NEW: a competitor appearing for the first time, or newly ranking for a tracked keyword. Each change carries the supporting source_url and fetched_at from the dossier. No source, no change entry.

  5. Rank changes by materiality (rank jumps on core keywords and price moves rank highest), and produce a one-line change digest for the briefing headline plus the structured change array for the dashboard.

  6. Return the change set to the caller. Do not write surfaces here; that is the merge and publish skills.

Edge cases

  • A competitor present last run but absent now: mark dropped in notes (do not invent a reason).
  • A field blocked this run but present last run: report "could not verify this run" rather than a false FALLING.
  • Timestamps missing on an old dossier: treat that field as not comparable.
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. 5d ago First seen · 46 lines · 75 tokens per session scan A 7f1fa668430e

Subscribe to this mod's changes

radar-diff-changes is a skill published in the GitHub repository sabahudin-web/competitive-intelligence-radar (3 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 543 once invoked, about $0.0004 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-31.

Marketing and SEOResearchagent-teamsbrightdataclaude-codeclaude-code-plugincompetitive-intelligencemarket-research
Related

Other skills, from other repositories

falsify

Adversarial falsification of sigint research findings. Generates disconfirming queries, executes web-only adversarial search, assigns ordinal verdicts (falsified | weakened | survived | inconclusive), and applies remediation (quarantine, confidence downgrade, follow-up queue). Invocable standalone via /sigint:falsify…

zircote-plugins/sigint · 100 tokens

regulatory-review

This skill should be used when the user asks to "analyze regulations", "regulatory landscape", "compliance requirements", "legal considerations", "regulatory risk", "industry regulations", "compliance analysis", "regulatory trends", or needs guidance on understanding regulatory environments, compliance requirements…

zircote-plugins/sigint · 68 tokens

tech-assessment

This skill should be used when the user asks to "assess technology", "technology evaluation", "tech stack analysis", "technical feasibility", "technology trends", "build vs buy", "technology roadmap", "architecture assessment", or needs guidance on evaluating technologies, technical due diligence, or technology…

zircote-plugins/sigint · 65 tokens

market-sizing

This skill should be used when the user asks to "calculate market size", "TAM SAM SOM analysis", "estimate market opportunity", "market sizing", "total addressable market", "serviceable market", "market potential", or needs guidance on market size estimation methodologies, market opportunity calculations, or growth…

zircote-plugins/sigint · 66 tokens

report-writing

This skill should be used when the user asks to "write a report", "executive summary", "research report format", "report structure", "present findings", "business writing", "analysis documentation", or needs guidance on structuring research outputs, executive communication, or professional report formatting.

zircote-plugins/sigint · 61 tokens

customer-research

This skill should be used when the user asks to "understand customers", "customer research", "user personas", "customer needs analysis", "buyer journey mapping", "voice of customer", "customer segmentation", "user research", or needs guidance on customer discovery methodologies, persona development, or understanding…

zircote-plugins/sigint · 66 tokens