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-publish-notiongit 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-publish-notion)<a href="https://agentmods.dev/skills/sabahudin-web/competitive-intelligence-radar/radar-publish-notion"><img src="https://agentmods.dev/badge/skills/sabahudin-web/competitive-intelligence-radar/radar-publish-notion/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-publish-notion"><img src="https://agentmods.dev/badge/skills/sabahudin-web/competitive-intelligence-radar/radar-publish-notion.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.00083 | $0.00668 |
| Opus 5 | $0.00042 | $0.00334 |
| Sonnet 5 | $0.00017 | $0.00134 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
radar-publish-notion 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
radar-publish-notion
Automation level: AUTONOMOUS once the databases exist and were approved at setup. If they do not
exist, route to radar-provision-notion (CHECKPOINT). See
automation-levels.md.
Goal: reflect the run in Notion with honest change tracking, idempotently.
Steps
-
Read
radar.config.json. Neednotion_prefix,competitors_ds,briefings_ds. If any is missing, stop and route toradar-provision-notion. -
Load the combined dossier JSON and the change set produced by
radar-merge-briefing. -
Upsert each competitor into the Competitors data source (matched by Domain):
- Find the existing row:
<notion_prefix>notion-searchor query the data source by Domain. - If found,
<notion_prefix>notion-update-pagewith this run's values and setChangefrom the change set (New, Rising, Falling, Steady) andLast Fetched. - If not found,
<notion_prefix>notion-create-pagesundercompetitors_ds. - Put each cited value in its column and the matching source URL in its paired Source column. Set Threat Level from the threat reading if present, else leave it unset rather than guessing.
- Find the existing row:
-
Create the Briefings page:
<notion_prefix>notion-create-pagesunderbriefings_dswith Title "Radar Briefing ", Run Date, Competitors Tracked, Key Changes (the one-line digest), War Room unchecked. The page body is the briefing markdown fromradar-merge-briefing(Notion markdown). Store the returned page id inlast_run.briefing_notion_page_idsoradar-publish-councilcan append to it. -
Obey no-em-dashes.md and no-fabrication.md in everything written: every web value keeps its source.
-
Return the Notion page link to the caller.
Edge cases
- A competitor matches more than one existing row (dirty data): update the most recently edited and note the duplicate; do not create a third.
- Notion rate limit or transient error: retry the single failed write a couple of times, then report exactly which competitor failed so the user can re-run; the upsert keying makes a re-run safe.
- Page body too long for one create: create the page with the summary, then append the rest with an update.
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 · 49 lines · 83 tokens per session scan A 963045738cac
radar-publish-notion is a skill published in the GitHub repository sabahudin-web/competitive-intelligence-radar (3 stars, last pushed 2mo ago), licensed MIT. It adds 83 tokens to every session and 668 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.
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…