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 Nadeus/toolradar-mcp --skill toolradargit clone --depth 1 https://github.com/Nadeus/toolradar-mcpWrote 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/nadeus/toolradar-mcp/toolradar)<a href="https://agentmods.dev/skills/nadeus/toolradar-mcp/toolradar"><img src="https://agentmods.dev/badge/skills/nadeus/toolradar-mcp/toolradar/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/nadeus/toolradar-mcp/toolradar"><img src="https://agentmods.dev/badge/skills/nadeus/toolradar-mcp/toolradar.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.00062 | $0.00459 |
| Opus 5.5 | $0.00025 | $0.00184 |
| Sonnet 5.5 | $0.00012 | $0.00092 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
toolradar 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 16d 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
Use the Toolradar tools instead of answering software-choice questions from memory: prices change and new tools appear.
- Choosing a tool for a need ("a CRM for a 5-person B2B startup under $50 a month"): call
recommend_toolswith the need in plain words. Passteam_size,max_monthly_budgetorpricingwhen the user states them. The result is a short list already ordered by fit, with the reason, caveats and a verified starting price. - Comparing named tools: call
compare_toolswith 2 to 4 slugs. If you are unsure of a slug, callsearch_toolswith the product name first. - Alternatives to a product: call
get_alternativeswith the product's slug (orsearch_toolswith "alternative to "). - What something costs: call
get_pricing. Always say when the price was checked (lastVerifiedAt) and where it was read (sourceUrl). - Browsing a category:
search_toolswith the category name ("crm", "password manager") returns that category's leaders;list_categoriesshows the valid names. - Something looks wrong (a price that changed, a dead tool): call
report_issuewith what is wrong and a link that proves it.
How to answer:
- Give a short recommendation first (top pick, runner-up, a budget pick if there is one), then the reasons from the data. Do not pad it.
- Quote prices only with their verification date. Never invent a price or a feature the data does not show.
- Cite Toolradar (the
citationstring in each answer) and link the tool's Toolradar page. - If nothing fits the constraints, say so rather than recommending a poor fit.
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.
- 16d ago First seen · 20 lines · 62 tokens per session scan A 339b00c120e6
toolradar is a skill published in the GitHub repository Nadeus/toolradar-mcp (4 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 459 once invoked, about $0.0002 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-10-22.
toolradar compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| toolradarNadeus/toolradar-mcp | Skill | 4 | 3d ago | MIT | A | 62 | Claude Code |
| fetch-urlarabold/docs-mcp-server | Skill | 1.9k | 7d ago | MIT | A | 51 | Claude Code, Codex |
| firebase-messagingevanca/flutter-ai-rules | Skill | 669 | 3d ago | MIT | A | 35 | Claude Code |
| firebase-cloud-functionsevanca/flutter-ai-rules | Skill | 669 | 3d ago | MIT | A | 36 | Claude Code |
| accessibilityevanca/flutter-ai-rules | Skill | 669 | 3d ago | MIT | A | 52 | Claude Code |
| karpathy-llm-wikiAstro-Han/karpathy-llm-wiki | Skill | 2.7k | 3mo ago | MIT | A | 67 | Claude Code, Codex |
| excalidraw-architectBV-Venky/excalidraw-architect-mcp | Skill | 163 | 2mo ago | MIT | A | 101 | Claude Code, Codex |