Borrowing it
Nothing to install: this file belongs to sabahudin-web/competitive-intelligence-radar. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sabahudin-web/competitive-intelligence-radar/main/CLAUDE.mdgit 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/instructions/sabahudin-web/competitive-intelligence-radar/claude-md)<a href="https://agentmods.dev/instructions/sabahudin-web/competitive-intelligence-radar/claude-md"><img src="https://agentmods.dev/badge/instructions/sabahudin-web/competitive-intelligence-radar/claude-md/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/instructions/sabahudin-web/competitive-intelligence-radar/claude-md"><img src="https://agentmods.dev/badge/instructions/sabahudin-web/competitive-intelligence-radar/claude-md.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.01247 | $0.01247 |
| Opus 5 | $0.00624 | $0.00624 |
| Sonnet 5 | $0.00249 | $0.00249 |
| Haiku 4.5 | $0.00125 | $0.00125 |
Grade A, and why
competitive-intelligence-radar CLAUDE.md 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 9d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code when working in the Competitive Intelligence Radar plugin repository.
What this project is
A Claude Code plugin that runs a weekly competitor radar for business owners and convenes a strategic war room on demand. It showcases the BrightData MCP for live web data and deliberately uses BOTH Claude Code parallelism primitives, each where it honestly fits.
/radar-setuponboards: asks about and live-tests the user's BrightData and Notion connection, shows the proposed Notion schema for approval, checks agent-team prerequisites./radaris the weekly GATHER: it fans out onecompetitor-scoutSUBAGENT per competitor in parallel; each gathers a cited dossier and reports back; the orchestrator diffs vs last run, merges one briefing, and publishes to three surfaces./radar-councilis the on-demand ANALYZE: it spins up a real experimental AGENT TEAM of four analyst teammates who message and challenge each other, then publishes a Strategic War Room addendum.
First thing to do in a fresh checkout
If the user has just installed or cloned this, point them to /radar-setup. Nothing else runs until
radar.config.json exists with verified MCP prefixes.
Architecture you must respect
- GATHER uses SUBAGENTS. Scouts are independent and only report back; they never message each other. Do not turn the gather into an agent team.
- DEBATE uses an AGENT TEAM. Analysts must see and challenge each other, which only a team allows. Do not turn the debate into plain subagents.
- The full rationale is in
rules/subagents-vs-agent-teams.md. Read it before changing either flow.
Hard rules (these are not optional)
These live in rules/. Every generated artifact must obey them:
no-fabrication.md: every factual claim carries a realsource_urlfetched this run plusfetched_at. No value without a source. Model knowledge is never a source.freshness.md: every field has a recency window and afetched_at; stale data is labeled, not presented as current.cost-control.md: prefer*_batchBrightData tools; cap competitors at 8; lean scout depth by default; the council is token heavy.automation-levels.md: AUTONOMOUS by default; CHECKPOINT for Notion database creation, for the MCP connection check at onboarding, for/radar-council, and for any GitHub push.no-em-dashes.md: never use the em dash (U+2014) or en dash (U+2013) anywhere, including in this file. Use commas, colons, or hyphens.
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.
- 9d ago First seen · 95 lines · 1,247 tokens per session scan A 07b513a54d92
competitive-intelligence-radar CLAUDE.md is an instructions file published in the GitHub repository sabahudin-web/competitive-intelligence-radar (3 stars, last pushed 2mo ago), licensed MIT. It adds 1,247 tokens to every session, about $0.0062 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.