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/optifeed/optifeed-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/rules/optifeed/optifeed-radar/cursor)<a href="https://agentmods.dev/rules/optifeed/optifeed-radar/cursor"><img src="https://agentmods.dev/badge/rules/optifeed/optifeed-radar/cursor/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/rules/optifeed/optifeed-radar/cursor"><img src="https://agentmods.dev/badge/rules/optifeed/optifeed-radar/cursor.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.00022 | $0.00450 |
| Opus 5.5 | $0.00009 | $0.00180 |
| Sonnet 5.5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
cursor 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 1mo 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
Optifeed Radar
Optifeed Radar is an open-source CLI and MCP server that asks real AI engines (ChatGPT, Perplexity, Gemini, Claude) real buyer questions and scores whether a brand gets recommended. It runs locally with the user's own API keys.
-
audit <domain>- free, no-key AI-readiness check. -
check <domain>- the scored AI Visibility Score. Needs at least one engine API key (OPENAI_API_KEY,ANTHROPIC_API_KEY,GOOGLE_API_KEY,PERPLEXITY_API_KEY); spends API credit: about $0.09 for one engine, $0.41 to $0.46 for all four, about $1.09 with--grounded. Cap it with--max-cost. Keys can be exported in the shell or put in a.envfile in the working directory. Acheck --quickacross four engines takes 47 to 51 seconds (about 97 with--grounded); that is the engines answering, not a hang. -
shopping <domain> --products "A, B, C"- product-level check (beta) for products the user names, in any order; each product is scored 0-100 and the report is ordered by what the engines did: products they answered about but never recommended lead, then the rest by visibility, then anything the run could not measure. Max 10 products, up to 4 prompts each per engine, so cap it with--max-cost.
Scores are estimates from sampling and vary between runs. Grounded engines are reported separately from parametric ones. Never log or store API keys. Catalog discovery (importing products from a store or a feed) and product-feed linting are on the roadmap, not shipped - join the waitlist at optifeed.com.
More at optifeed.com
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.
- 1mo ago First seen · 36 lines · 22 tokens per session scan A 6d3df731bf35
cursor is a cursor rule published in the GitHub repository optifeed/optifeed-radar (5 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 450 once invoked, about $0.0001 per session on Opus 5.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 cursor rules, from other repositories
emergency-fund
Size an emergency fund from essential spend and real risk factors — not a one-size 'six months' — with the funding timeline and where the money should sit. Use when asked how big should my emergency fund be, do I have enough saved, emergency fund or invest, or how many months of expenses do I need. Produces the…
delta-briefing
Make a recurring brief report what changed since the last edition instead of restating everything. Use when a weekly or monthly report keeps repeating itself, when setting up a scheduled monitor or digest, or when asked to make a recurring update delta-aware. Produces a changes-first brief plus the state record the…
explorer-interface-brief
Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Produces, from a topic, the UI design brief (audience, layout, panels, interactions, label style, colour palette, accessibility) and an…
voice-agent-design
Design a voice AI agent for phone or in-app conversations — call flows, interruption handling, escalation to humans, and the metrics that catch a bad voice experience. Use when asked to design a voice agent, automate a phone line, spec an IVR replacement, or review why callers hate an existing voice bot. Produces a…
respite-care-plan
Plan a genuine break from caregiving — arrange the coverage, hand off the essentials, and actually rest — because respite is what lets you keep going. Use when asked I need a break from caregiving, how do I arrange respite care, I can't leave them alone, or help me get time off from caring. Produces the coverage…
agent-spec
Specify an autonomous or tool-using AI agent before building it. Use when asked to design an AI agent, define an agent's tools and guardrails, scope what an agent is allowed to do, or write an agent spec/PRD. Produces an agent spec — goal & scope, tools with permissions, the control loop, guardrails & approval gates…