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 danielrosehill/Claude-Open-Router-Model-Research-Plugin --skill or-find-tool-modelsgit clone --depth 1 https://github.com/danielrosehill/Claude-Open-Router-Model-Research-PluginWrote 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/danielrosehill/claude-open-router-model-research-plugin/or-find-tool-models)<a href="https://agentmods.dev/skills/danielrosehill/claude-open-router-model-research-plugin/or-find-tool-models"><img src="https://agentmods.dev/badge/skills/danielrosehill/claude-open-router-model-research-plugin/or-find-tool-models/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/danielrosehill/claude-open-router-model-research-plugin/or-find-tool-models"><img src="https://agentmods.dev/badge/skills/danielrosehill/claude-open-router-model-research-plugin/or-find-tool-models.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.00073 | $0.00480 |
| Opus 5 | $0.00036 | $0.00240 |
| Sonnet 5 | $0.00015 | $0.00096 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
or-find-tool-models scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://openrouter.ai/api/v1/models -H "Accept: application/json" What it actually says
Find OpenRouter Tool-Calling Models
Filter the OpenRouter catalog to models that declare tool/function calling support, then rank or summarize them based on the user's stated criteria (price, context, provider).
When to use
The user wants to discover models suitable for agentic / tool-using workflows on OpenRouter — function calling, MCP, code agents, structured tool invocation.
Workflow
- Fetch the catalog:
curl -s https://openrouter.ai/api/v1/models -H "Accept: application/json" - Filter
data[]wheresupported_parametersincludes"tools". Optionally also require"tool_choice"for stricter filtering. - If the user expressed preferences (cheapest, largest context, specific provider), apply them:
- Cheapest — sort by
pricing.completionascending - Largest context — sort by
context_lengthdescending - Provider — filter
idby prefix (openai/,anthropic/,google/,meta-llama/, etc.)
- Cheapest — sort by
- If the user did not state criteria, ask one short clarifying question: budget ceiling? minimum context? preferred providers?
- Return the top 5–10 matches as a markdown table: ID, Context, Prompt $/1M, Completion $/1M, Other supported params.
Notes
- Prices in the catalog are USD per token. Multiply by 1,000,000 for $/1M-token display.
- Some models list
toolsbut have caveats noted in their description — surface those if relevant. - Free models (pricing all
"0") often have rate limits and lower reliability — flag this when recommending free models.
Output
Markdown table sorted by the user's stated criterion (default: cheapest completion price). Include a one-line summary of how many tool-capable models exist in the catalog total.
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.
- 12d ago First seen · 37 lines · 73 tokens per session scan A f899337a92e6
or-find-tool-models is a skill published in the GitHub repository danielrosehill/Claude-Open-Router-Model-Research-Plugin (2 stars, last pushed 4mo ago), licensed MIT. It adds 73 tokens to every session and 480 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…