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 ccplugins/awesome-claude-code-plugins --skill insider-radargit clone --depth 1 https://github.com/ccplugins/awesome-claude-code-pluginsWrote 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/ccplugins/awesome-claude-code-plugins/insider-radar)<a href="https://agentmods.dev/skills/ccplugins/awesome-claude-code-plugins/insider-radar"><img src="https://agentmods.dev/badge/skills/ccplugins/awesome-claude-code-plugins/insider-radar/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/ccplugins/awesome-claude-code-plugins/insider-radar"><img src="https://agentmods.dev/badge/skills/ccplugins/awesome-claude-code-plugins/insider-radar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00074 | $0.00555 |
| Opus 5.5 | $0.00030 | $0.00222 |
| Sonnet 5.5 | $0.00015 | $0.00111 |
| Haiku 4.5 | $0.00007 | $0.00056 |
Grade A, and why
insider-radar 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
Insider radar
Surface ownership-change signal: SEC Form 4 trades (officers, directors, 10% owners trading their own stock) and 13F moves (funds and foundations adjusting stakes). AlphaAI templates each filing into a relevance-scored news row, so the read-across is already done.
Steps
- Single ticker. Call
alphai_insider_news(ticker="<SYM>"). If the user wants only the strongest signal, raise the floor withmin_relevance=8. - Watchlist. Call
alphai_insider_news(ticker=...)once per name. If the user gave none, callalphai_insider_news()unfiltered for the broad tape. - Time-box on request. For "this week" / "since earnings", pass
from_date(ISO, UTC). Paginate withcursoronly if they ask for more. - Distinguish buys from sells. Open-market purchases by insiders are the higher-signal event; routine 10b5-1 scheduled sales and option-exercise sales are noise more often than not. Call that out — don't treat every sale as bearish.
Output
- Notable buys — insider purchases first: ticker · who/role · size if given · relevance. These are what most users actually want.
- Notable sells — flag whether each looks like a discretionary sale vs a scheduled/10b5-1 or option-related sale, where the feed says.
- Institutional (13F) — any fund stake increases/trims worth a mention.
- Read — one line: is the cluster leaning accumulation or distribution, or is it just routine?
Guardrails
- An insider sale is not automatically bearish (taxes, diversification, scheduled plans). Say what the filing shows; don't over-read it.
- One filing can span several tranches sharing a row — report the event, not a count of line items.
- Lead with
relevance_score; "no notable insider activity in the window" is a valid, useful answer. - News, not advice.
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 · 45 lines · 74 tokens per session scan A fd84f2762296
insider-radar is a skill published in the GitHub repository ccplugins/awesome-claude-code-plugins (977 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 74 tokens to every session and 555 once invoked, about $0.0003 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…