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/tavily-ai/tavily-cursor-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/commands/tavily-ai/tavily-cursor-plugin/tavily-setup)<a href="https://agentmods.dev/commands/tavily-ai/tavily-cursor-plugin/tavily-setup"><img src="https://agentmods.dev/badge/commands/tavily-ai/tavily-cursor-plugin/tavily-setup/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/commands/tavily-ai/tavily-cursor-plugin/tavily-setup"><img src="https://agentmods.dev/badge/commands/tavily-ai/tavily-cursor-plugin/tavily-setup.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.00021 | $0.00232 |
| Opus 5 | $0.00010 | $0.00116 |
| Sonnet 5 | $0.00004 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
tavily-setup 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 3d 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
Tavily Plugin Setup
Pick one primary surface. Prefer MCP when Tavily tools are callable.
Native plugin host (Cursor desktop, Grok Bot, connectors)
- If a Tavily MCP search tool is callable, run one live search for
Tavily Search API. If it succeeds, setup is complete. Do not install the CLI. - If MCP tools are present but not authenticated, complete the host's OAuth flow for
https://mcp.tavily.com/mcp. Never ask the user to paste an API key into chat. - If this host does not use the Tavily CLI, stop after MCP is callable.
Terminal coding agent (Cursor CLI, Claude Code, Codex CLI)
Use the tavily-cli skill to install and authenticate tvly, then run one live tvly search "Tavily Search API" --client-name "cursor plugin" --max-results 1 --json. A successful CLI request does not prove MCP is connected.
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.
- 3d ago Changed · -74 lines · +3 tokens per session scan C → A 1da655a39a8d
- 8d ago First seen · 93 lines · 18 tokens per session scan C 71b450a05e03
tavily-setup is a command published in the GitHub repository tavily-ai/tavily-cursor-plugin (2 stars, last pushed 7d ago), licensed MIT. It adds 21 tokens to every session and 232 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.