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.
npx skills add sabahudin-web/competitive-intelligence-radar --skill radar-onboardgit clone --depth 1 https://github.com/sabahudin-web/competitive-intelligence-radarWrote 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.
[](https://agentmods.dev/skills/sabahudin-web/competitive-intelligence-radar/radar-onboard)<a href="https://agentmods.dev/skills/sabahudin-web/competitive-intelligence-radar/radar-onboard"><img src="https://agentmods.dev/badge/skills/sabahudin-web/competitive-intelligence-radar/radar-onboard/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.
<a href="https://agentmods.dev/skills/sabahudin-web/competitive-intelligence-radar/radar-onboard"><img src="https://agentmods.dev/badge/skills/sabahudin-web/competitive-intelligence-radar/radar-onboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00104 | $0.01070 |
| Opus 5 | $0.00052 | $0.00535 |
| Sonnet 5 | $0.00021 | $0.00214 |
| Haiku 4.5 | $0.00010 | $0.00107 |
Grade A, and why
radar-onboard 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
radar-onboard
Automation level: CHECKPOINT. You ask the user real questions and you stop if a live MCP test fails. Never assume a connection. See automation-levels.md.
Goal: produce a complete radar.config.json (schema in
config-schema.md) with verified MCP prefixes, so every later
skill just works.
Steps
-
Greet and explain in two lines what the radar does and that it needs BrightData (web data) and Notion (publishing). Keep branding generic; this plugin serves any business.
-
ASK about connections, do not assume: "Have you connected BrightData and Notion? I usually see two paths: through this plugin, or through the Claude Desktop app connectors. I will test both."
-
Detect the live BrightData prefix. Try a tiny real call in this order until one works, using a harmless query:
- Plugin path:
mcp__plugin_competitive-intelligence-radar_brightdata__search_engine - Desktop path:
mcp__claude_ai_Bright-Data__search_engine - Any other connected BrightData server visible in this session (a UUID prefix is normal).
Use query like
{"query": "site:example.com", "engine": "google"}. The FIRST prefix that returns a result is the live one. Recordmcp.brightdata_prefixandmcp.brightdata_verified_at.
- Plugin path:
-
Detect the live Notion prefix. Try a tiny real read, for example
notion-get-usersor anotion-searchwith a simple query, in this order:mcp__plugin_competitive-intelligence-radar_notion__mcp__claude_ai_Notion__- Any other connected Notion server (UUID prefix).
Record
mcp.notion_prefixandmcp.notion_verified_at.
-
If EITHER test fails, STOP. Do not write a half-config that pretends a connection exists. Tell the user exactly how to connect:
- BrightData: get a free token at brightdata.com, then either set
BRIGHTDATA_API_TOKENin the environment so this plugin's.mcp.jsonserver starts, or add BrightData in the Claude Desktop app connectors. Re-run/radar-setupafter. - Notion: connect Notion via OAuth, either through this plugin's Notion server or the Desktop app connectors. Re-run after.
- BrightData: get a free token at brightdata.com, then either set
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.
- 11d ago First seen · 75 lines · 104 tokens per session scan A 89645182c66b
radar-onboard is a skill published in the GitHub repository sabahudin-web/competitive-intelligence-radar (3 stars, last pushed 2mo ago), licensed MIT. It adds 104 tokens to every session and 1,070 once invoked, about $0.0005 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.
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…
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…
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.
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…
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.
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…