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-provision-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-provision-notion)<a href="https://agentmods.dev/skills/sabahudin-web/competitive-intelligence-radar/radar-provision-notion"><img src="https://agentmods.dev/badge/skills/sabahudin-web/competitive-intelligence-radar/radar-provision-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-provision-notion"><img src="https://agentmods.dev/badge/skills/sabahudin-web/competitive-intelligence-radar/radar-provision-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.00096 | $0.00661 |
| Opus 5 | $0.00048 | $0.00331 |
| Sonnet 5 | $0.00019 | $0.00132 |
| Haiku 4.5 | $0.00010 | $0.00066 |
Grade A, and why
radar-provision-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-provision-notion
Automation level: CHECKPOINT. Showing the schema and getting approval BEFORE creating any database is a hard requirement. See automation-levels.md.
Prerequisite: radar.config.json exists with a verified notion_prefix. If not, route the user to
radar-onboard.
Steps
-
Idempotency check first. Read
radar.config.json. Ifnotion.competitors_dsandnotion.briefings_dsare already set, verify they still resolve with anotion-fetch. If both resolve, report "Notion already provisioned" and stop. Do not create duplicates. -
SHOW the proposed schema for both databases, exactly as laid out in notion-schema.md: the Competitors database columns and the Briefings database columns, in a readable table. Then ask, in plain words: "Do you like this schema, or do you want changes (rename, add, or drop any field)?" STOP and wait for an answer. Do not proceed on silence.
-
Incorporate any requested changes into the DDL. Re-show if the changes are non-trivial and confirm again.
-
Only after approval, create the databases under the chosen parent (
notion.parent_page_id, or workspace level if empty), using the Notioncreate-databasetool (<notion_prefix>notion-create-database) with the approvedCREATE TABLEDDL. Create the Competitors database first, then the Briefings database. -
Capture the returned database id AND the
<data-source>id for each, and write all four intoradar.config.json(competitors_db,competitors_ds,briefings_db,briefings_ds). Pages are later created under the data source ids. -
Confirm to the user with the Notion links and a one-line note that publishing is now enabled.
Edge cases
- Parent page not accessible to the Notion integration: stop and tell the user to share the parent page with the connected Notion integration, then re-run.
- User wants to reuse an existing database: accept its database url,
notion-fetchit to get the data source id, store the ids, and skip creation. Verify the columns cover what publishing needs; warn about any missing column rather than silently failing later. - Partial creation (Competitors created, Briefings failed): save what succeeded so a re-run is idempotent and only creates the missing one.
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 · 0 tokens per session scan A bee1397c40f3
radar-provision-notion is a skill published in the GitHub repository sabahudin-web/competitive-intelligence-radar (3 stars, last pushed 2mo ago), licensed MIT. It adds 96 tokens to every session and 661 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…