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/gleanwork/cursor-plugins/glean-result-vettinggit clone --depth 1 https://github.com/gleanwork/cursor-pluginsWhat 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.00217 | $0.00217 |
| Opus 5 | $0.00109 | $0.00109 |
| Sonnet 5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
glean-result-vetting 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 2d 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 Result Vetting
When presenting results from Glean MCP tools, always vet before showing:
Relevance: Does this actually answer the question, or just contain matching keywords? Reject keyword coincidences.
Freshness: Is this current?
- ✅ <6 months: include with confidence
- ⚠️ 6-12 months: include with staleness note
- ❌ 12+ months: exclude unless no alternatives (with strong warning)
Authority: How reliable is the source?
- Official (RFCs, approved specs) > Semi-official (team wikis) > Informal (Slack, personal notes)
Quality over quantity: 3 vetted results beats 10 unvetted mentions. "Nothing relevant found" is a valid and useful answer — never pad with weak results.
Always include: document title, URL, last updated date, and confidence level when presenting Glean results.
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.
- 2d ago First seen · 23 lines · 217 tokens per session scan A 8149223909d1
glean-result-vetting is a cursor rule published in the GitHub repository gleanwork/cursor-plugins (4 stars, last pushed 12d ago), licensed MIT. It adds 217 tokens to every session, about $0.0011 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
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.