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.
git 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/commands/sabahudin-web/competitive-intelligence-radar/radar-setup)<a href="https://agentmods.dev/commands/sabahudin-web/competitive-intelligence-radar/radar-setup"><img src="https://agentmods.dev/badge/commands/sabahudin-web/competitive-intelligence-radar/radar-setup.svg" alt="Measured on agentmods" 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.00055 | $0.00470 |
| Opus 5 | $0.00028 | $0.00235 |
| Sonnet 5 | $0.00011 | $0.00094 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
radar-setup 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 7d 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.
What it actually says
/radar-setup
You are orchestrating setup. This command is CHECKPOINT throughout: it asks before it acts. It calls skills in order and stops on any failure. Do the work through the skills; this file only sequences them. See automation-levels.md.
Sequence
-
Run the
radar-onboardskill. It ASKS whether BrightData and Notion are connected, live-tests one real call to each, detects the live MCP prefix for each (plugin path, desktopclaude_aipath, or a UUID prefix), and writesradar.config.jsonwith the user's business context. If either live test fails, it STOPS with connection instructions. Do not continue past a failed test. -
Run the
radar-provision-notionskill. It SHOWS the proposed Competitors and Briefings schema and asks "do you like this, or want changes?" It creates the databases ONLY after the user approves, and is idempotent if they already exist. Store the database and data source ids in the config. -
Check the agent-teams prerequisites for
/radar-counciland report status to the user (do not try to fix their settings silently):- Claude Code version is v2.1.32 or later (
claude --version). CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMSis set to1in settings or environment. If either is missing, show the exact fix from agent-teams-setup.md. Gather and the council are independent: the user can run/radareven if the council prerequisites are not met yet.
- Claude Code version is v2.1.32 or later (
-
Summarize: what was verified, what was created in Notion, whether the council is ready, and that the next step is
/radar.
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.
- 7d ago First seen · 32 lines · 55 tokens per session scan A 8a545a9f4ed4
radar-setup is a command published in the GitHub repository sabahudin-web/competitive-intelligence-radar (3 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 470 once invoked, about $0.0003 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 commands, from other repositories
status
Show current research session state and progress.
resume
Resume a previous research session from progress file.
init
Manually initialize or reload research context for sigint.
falsify
Adversarially falsify research findings via web-only disconfirming search; quarantine, downgrade, or annotate findings based on verdicts.
augment
Deep-dive into a specific area of current research.
issues
Create GitHub issues from research findings as atomic deliverables.