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/johnnichev/selectoolsWrote 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/johnnichev/selectools/selectools-providers)<a href="https://agentmods.dev/rules/johnnichev/selectools/selectools-providers"><img src="https://agentmods.dev/badge/rules/johnnichev/selectools/selectools-providers/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/johnnichev/selectools/selectools-providers"><img src="https://agentmods.dev/badge/rules/johnnichev/selectools/selectools-providers.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.00000 | $0.00493 |
| Opus 5.5 | $0.00000 | $0.00197 |
| Sonnet 5.5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
selectools-providers 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
Provider Implementation Rules
Protocol Compliance
Every provider must implement all methods from providers/base.py:
complete(),acomplete()— sync/async completionstream(),astream()— sync/async streaming_format_messages()— convertMessageto provider format
Critical: Tool Passing
ALL methods (complete, acomplete, stream, astream) MUST:
- Accept
tools: list[Tool] | None = Noneparameter - Forward tools to the underlying API call
- Map tools using
_map_tool_to_<provider>(t)helper
Critical: Streaming Return Types
stream()returnsIterable[str]astream()returnsAsyncIterable[Union[str, ToolCall]]astream()must parse tool call chunks and yieldToolCallobjects- Never stringify
ToolCallobjects
OpenAI-Specific
- Use
_uses_max_completion_tokens(model)to decide parameter name - GPT-5.x, o-series, GPT-4.1 need
max_completion_tokens - Older models use
max_tokens
FallbackProvider
astream()must include try/except with_is_retriable+ circuit breaker- Use
_record_failure()/_record_success()consistently - Call
on_fallbackcallback when falling back
Message Formatting
Role.TOOLmessages need provider-specific formatting:- OpenAI:
{"role": "tool", "content": ..., "tool_call_id": ...} - Anthropic:
{"role": "user", "content": [{"type": "tool_result", ...}]} - Gemini:
{"role": "user", "parts": [{"function_response": ...}]} - Ollama:
{"role": "tool", "content": ..., "tool_call_id": ...}
- OpenAI:
Testing
- Use
RecordingProviderto capture and assert exact args - Test
_format_messagesfor TOOL role, ASSISTANT with tool_calls, images - Test
astream()yieldsToolCallobjects (not just strings) - Test FallbackProvider failover, circuit breaker, and callback behavior
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 · 49 lines · 0 tokens per session scan A 1b842c107d7f
selectools-providers is a cursor rule published in the GitHub repository johnnichev/selectools (11 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 493 tokens. 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 cursor rules, from other repositories
agentguard
AgentGuard local-first safety.
skill-mcp-server
Padrões DARE para servidores MCP (Model Context Protocol da Anthropic) em TypeScript ou Python. Tools, resources, prompts; transports stdio/SSE/HTTP; validação Zod/Pydantic; autorização por tool; observabilidade; testes; publicação.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.