agentmods.dev

radar-plan-targets

radar-plan-targets is a skill for Claude Code from sabahudin-web/competitive-intelligence-radar. It costs 88 tokens per session (505 once invoked), scanned A, original, MIT.

A planning step that turns radar settings into a list of competitor research jobs. It reads the configuration, limits the run to eight competitors, and prepares one job description per competitor.

In plain words
What is it for?
Use it as the first step of `/radar` after setup to plan competitor scouting jobs and organize their dossier files.
Why use it?
It gives a research run clear targets, search terms, locations, freshness limits, and output files before work is distributed.

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 3repo 2mo ago A scan 88 tokens original MIT

Good fit Use it as the first step of /radar after setup to plan competitor scouting jobs and organize their dossier files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sabahudin-web/competitive-intelligence-radar/radar-plan-targets
View source ↗ 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.

Any agent
npx skills add sabahudin-web/competitive-intelligence-radar --skill radar-plan-targets
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-plan-targets

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/sabahudin-web/competitive-intelligence-radar/radar-plan-targets"><img src="https://agentmods.dev/badge/skills/sabahudin-web/competitive-intelligence-radar/radar-plan-targets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 505 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.00088 $0.00505
Opus 5 $0.00044 $0.00253
Sonnet 5 $0.00018 $0.00101
Haiku 4.5 $0.00009 $0.00051

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

Security

Grade A, and why

radar-plan-targets 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 12d 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-plan-targets/SKILL.md · 43 lines

What it actually says

radar-plan-targets

Automation level: AUTONOMOUS. This is read-and-plan only; it spawns nothing.

Goal: turn the config into a clean list of scout jobs the /radar command will fan out in one message. See cost-control.md for the caps.

Steps

  1. Read radar.config.json. If missing or missing a verified brightdata_prefix, stop and route the user to /radar-setup.

  2. Establish the run id and output directory: a date-stamped run, for example outputs/dossiers/<YYYY-MM-DD>/. Create the directory. Each scout writes one file <competitor-slug>.json there.

  3. Apply caps: take at most the first 8 competitors. If more were configured, note which were skipped. Plan waves of at most 8 (normally one wave given the cap).

  4. For each competitor, build a job spec the scout understands:

    • COMPETITOR: name + domain
    • MY_KEYWORDS: from config
    • GEO: config geo
    • SCOUT_DEPTH: the three flags from config
    • BRIGHTDATA_PREFIX: the verified prefix from config
    • OUTPUT_PATH: outputs/dossiers/<run-date>/<slug>.json
    • FRESHNESS: the news/funding/sentiment day windows (config overrides or the defaults in freshness.md)

  5. Return the job list and the run directory to the caller. Do not gather anything yourself.

Edge cases

  • Zero competitors configured: stop and tell the user to add competitors via radar-onboard.
  • Duplicate domains: dedupe, keep the first.
  • A competitor missing a domain: keep the name, let the scout resolve the domain via search; mark it so the scout knows to confirm the domain first.
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. 12d ago First seen · 43 lines · 88 tokens per session scan A d7c6d13481b9

Subscribe to this mod's changes

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

Claude CodePlanningResearchagent-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