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 agentmods add rules/sijeeshmiziha/visionagent/think-toolgit clone --depth 1 https://github.com/sijeeshmiziha/visionagentWrote 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/sijeeshmiziha/visionagent/think-tool)<a href="https://agentmods.dev/rules/sijeeshmiziha/visionagent/think-tool"><img src="https://agentmods.dev/badge/rules/sijeeshmiziha/visionagent/think-tool.svg" alt="Measured on agentmods" 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 | $0.00403 | $0.00403 |
| Opus 5 | $0.00201 | $0.00201 |
| Sonnet 5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
think-tool 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 5d 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
Think Tool / Reasoning During Tool Use
Extended Thinking vs Think Tool
- Prefer extended thinking when the provider supports it and the task is simpler (e.g. planning before acting, or no need to reason over tool outputs). Use the platform’s extended-thinking feature where available.
- Consider a "think" tool when the model must reason after receiving tool results (e.g. long chains of tool calls, policy checks, or sequential decisions where each step depends on previous outputs). The think tool is a no-side-effect tool (e.g. single
thoughtstring, handler that only logs or appends to the trace) so the model can “stop and think” between tool rounds.
When to Add a Think Tool
- Add when: long chains of tool calls; policy-heavy or compliance-sensitive flows; sequential decisions where mistakes are costly; or the model needs to analyze tool output (e.g. verify rules, check completeness) before acting.
- Skip when: single or parallel tool calls only; simple instruction following with few constraints; or extended thinking already covers the needed reasoning.
Implementation
- Tool: Minimal spec (e.g. one parameter such as
thought); handler has no side effects (log/trace only). Description should state that it does not change state and is for reasoning/scratchpad use. - Prompting: Provide domain-specific examples in the system prompt for when and how to use the tool (e.g. list applicable rules, verify information is complete, check compliance before acting). Put longer or complex guidance in the system prompt rather than only in the tool description.
- Cost: Think tool increases output tokens but does not change external behavior unless the model uses it; low downside to including it when the scenario matches.
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.
- 5d ago First seen · 23 lines · 403 tokens per session scan A 84c77c3298a2
think-tool is a cursor rule published in the GitHub repository sijeeshmiziha/visionagent (2 stars, last pushed 5mo ago), licensed MIT. It adds 403 tokens to every session, about $0.0020 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 cursor rules, from other repositories
solidity-foundry-cursorrules-prompt-file
Cursor rule "solidity-foundry-cursorrules-prompt-file" from ItamarZand88/awesome-agent-conventions, covering do not compile tests when compiling via-ir and don't pollute bytecode with metadata.
database
Cursor rule "database" from ItamarZand88/awesome-agent-conventions, covering database best practices, prisma setup, prisma models, prisma queries and supabase setup.
grug-brained-dev_simple-tools
Choose tools and libraries that are simple and well-understood.
java-springboot-jpa-cursorrules-prompt-file
description: "Cursor rules for Java development with Springboot and JPA integration." globs: / alwaysApply: false.
angular-typescript-cursorrules-prompt-file
description: "Cursor rules for Angular development with TypeScript integration." globs: / alwaysApply: false.
fortran
Cursor rule "fortran" from ItamarZand88/awesome-agent-conventions, covering fortran programming guidelines, basic principles, kinds and types, naming and style and procedures.