agentmods.dev

radar-merge-briefing

radar-merge-briefing is a skill for Claude Code from sabahudin-web/competitive-intelligence-radar. It costs 71 tokens per session (1,216 once invoked), scanned A, original, MIT.

A report-building step that combines competitor research files and a list of recent changes into one briefing. It also creates raw research data and dashboard data, with a source link attached to every claim.

In plain words
What is it for?
Use it after competitor changes have been detected and before publishing the results to Notion or an HTML dashboard.
Why use it?
It prevents information from being scattered across separate files and makes unsupported or outdated claims visible. Missing or blocked information is recorded plainly instead of being filled in.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

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

not rated 3repo 2mo ago A scan 71 tokens original MIT

Good fit Use it after competitor changes have been detected and before publishing the results to Notion or an HTML dashboard.

Compare 6 skills from other repositories ↓
View source ↗ sabahudin-web/competitive-intelligence-radar linkedin.com
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add sabahudin-web/competitive-intelligence-radar
Claude Code
/plugin install 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-merge-briefing

README.md
[![agentmods](https://agentmods.dev/badge/skills/sabahudin-web/competitive-intelligence-radar/radar-merge-briefing/github.svg)](https://agentmods.dev/skills/sabahudin-web/competitive-intelligence-radar/radar-merge-briefing)
Your own site
<a href="https://agentmods.dev/skills/sabahudin-web/competitive-intelligence-radar/radar-merge-briefing"><img src="https://agentmods.dev/badge/skills/sabahudin-web/competitive-intelligence-radar/radar-merge-briefing/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 radar-merge-briefing

Your own site · 80×15
<a href="https://agentmods.dev/skills/sabahudin-web/competitive-intelligence-radar/radar-merge-briefing"><img src="https://agentmods.dev/badge/skills/sabahudin-web/competitive-intelligence-radar/radar-merge-briefing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,216 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.00071 $0.01216
Opus 5 $0.00036 $0.00608
Sonnet 5 $0.00014 $0.00243
Haiku 4.5 $0.00007 $0.00122

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

Security

Grade A, and why

radar-merge-briefing 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 11d 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-merge-briefing/SKILL.md · 90 lines

How it starts

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

radar-merge-briefing

Automation level: AUTONOMOUS.

Goal: produce the single source of truth for this run on local disk, with a source URL on every claim and no fabricated or stale-as-fresh values.

Steps

  1. Inputs from the caller: the run date, the run dossier directory, and the change set from radar-diff-changes. Read radar.config.json for business name, keywords, and freshness windows.

  2. Load every dossier in the run directory.

  3. Render the briefing markdown from the template at ${CLAUDE_PLUGIN_ROOT}/assets/briefing-template.md. Fill every placeholder. For each competitor field, write the value, its source link, the fetched date, and the status. Where a field is not_found or blocked, say so plainly rather than leaving a gap or inventing a value. Build the "What changed" and "Focus list" sections from the ranked change set.

  4. Enforce the rules as you write:

  5. Write three files:

    • Briefing markdown: outputs/briefings/<YYYY-MM-DD>-briefing.md
    • Combined raw dossier JSON: outputs/dossiers/<YYYY-MM-DD>/combined.json (all dossiers plus the change set, the machine-readable record).
    • Dashboard data JSON: outputs/dashboard/<YYYY-MM-DD>-data.json, shaped for the dashboard template (see the shape below). war_room is null until /radar-council fills it.

  6. Update radar.config.json last_run with the new paths and date, and roll the previous run's dossier dir so the next diff has a baseline.

Dashboard data JSON shape

The dashboard at ${CLAUDE_PLUGIN_ROOT}/assets/dashboard-template.html reads this exact shape. The template computes missing KPIs itself, but populate kpis so the numbers match the briefing. SERP rank values MUST be numbers (not strings) so the leaderboard renders. Sentiment values are one of positive, mixed, negative, unknown. Each change carries a type (RISING, FALLING, PRICE, NEWS, NEW, STEADY) and the competitor name.

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

Subscribe to this mod's changes

radar-merge-briefing is a skill published in the GitHub repository sabahudin-web/competitive-intelligence-radar (3 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 1,216 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.

Analytics and metricsClaude CodeResearchagent-teamsbrightdataclaude-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

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

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

augment

Deep-dive into a specific area of current research. Orchestrates a single dimension-analyst using full swarm pattern (TeamCreate, TaskCreate, SendMessage). Use when the user wants to augment current research with deeper analysis of a specific area.

zircote-plugins/sigint · 53 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