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/gleanwork/cursor-pluginsWrote 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/gleanwork/cursor-plugins/glean-tool-selection)<a href="https://agentmods.dev/rules/gleanwork/cursor-plugins/glean-tool-selection"><img src="https://agentmods.dev/badge/rules/gleanwork/cursor-plugins/glean-tool-selection/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/gleanwork/cursor-plugins/glean-tool-selection"><img src="https://agentmods.dev/badge/rules/gleanwork/cursor-plugins/glean-tool-selection.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.00288 | $0.00288 |
| Opus 5.5 | $0.00115 | $0.00115 |
| Sonnet 5.5 | $0.00058 | $0.00058 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
glean-tool-selection 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
Glean Tool Selection
When Glean MCP tools are available (tools matching mcp__glean_*), use the correct tool for each query type:
- People queries ("who works on", "who owns", org chart) →
employee_search(NEVER usesearchfor people) - Meeting queries (decisions, action items, transcripts) →
meeting_lookupwith natural language dates - Email queries (messages, attachments) →
gmail_search - Code queries (implementations, patterns, commits) →
code_search - Activity queries ("what have I done", standup prep) →
user_activity - Document queries (policies, specs, wikis) →
search - Full document content →
read_documentwith URL from search results - Complex multi-source analysis →
chat
Key rules:
- Use
searchwith structured parameters (separateowner,app,updatedarguments) - Use
code_search,employee_search,gmail_searchwith inline query filters - Use
meeting_lookupwith natural language dates (inline date filters are unreliable) - Always cite sources with URLs so users can verify
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 · 24 lines · 288 tokens per session scan A a5d611f54039
glean-tool-selection is a cursor rule published in the GitHub repository gleanwork/cursor-plugins (4 stars, last pushed 17d ago), licensed MIT. It adds 288 tokens to every session, about $0.0012 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-08-31.
Other cursor rules, from other repositories
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.