What is glean-result-vetting?

An always-on rule for checking results returned by Glean, a tool for searching an organisation’s documents and knowledge. It checks whether each result is relevant, recent, and from a reliable source.

Use it whenever presenting Glean search results to decide which documents to include and how strongly to trust them.

It helps prevent search answers from being padded with keyword matches, outdated documents, or informal notes. It also requires useful source details such as the title, link, update date, and confidence.

glean-result-vetting — Cursor rule for Cursor by gleanwork

Install

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.

Clone the repo

git clone --depth 1 https://github.com/gleanwork/cursor-plugins

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/gleanwork/cursor-plugins/glean-result-vetting/github.svg)](https://agentmods.dev/rules/gleanwork/cursor-plugins/glean-result-vetting)

Your own site

<a href="https://agentmods.dev/rules/gleanwork/cursor-plugins/glean-result-vetting"><img src="https://agentmods.dev/badge/rules/gleanwork/cursor-plugins/glean-result-vetting/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/gleanwork/cursor-plugins/glean-result-vetting"><img src="https://agentmods.dev/badge/rules/gleanwork/cursor-plugins/glean-result-vetting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 217 This file is loaded in full into every session.

When invoked 217 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00217	$0.00217
Opus 5.5	$0.00087	$0.00087
Sonnet 5.5	$0.00043	$0.00043
Haiku 4.5	$0.00022	$0.00022

Measured 2mo ago against content hash 8149223909d1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

glean/rules/glean-result-vetting.mdc · 23 lines

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.

Changes

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.

2mo ago First seen · 23 lines · 217 tokens per session scan A 8149223909d1

Subscribe to this mod's changes

glean-result-vetting is a cursor rule published in the GitHub repository gleanwork/cursor-plugins (4 stars, last pushed 10d ago), licensed MIT. It adds 217 tokens to every session, about $0.0009 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.

Research

glean-result-vetting next to 6 cursor rules from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
glean-result-vettinggleanwork/cursor-plugins	Cursor rule	4	10d ago	MIT	A	217	Cursor
ponytailDietrichGebert/ponytail	Cursor rule	186k	9d ago	MIT	A	604	Cursor
angular-20angular/angular	Cursor rule	101k	yesterday	MIT	A	0	Cursor
dev-standardapache/superset	Cursor rule	75k	yesterday	Apache-2.0	A	1,147	Cursor
control-plane-descriptorsprisma/orm	Cursor rule	48k	yesterday	Apache-2.0	A	0	Cursor
family-instance-domain-actionsprisma/orm	Cursor rule	48k	yesterday	Apache-2.0	A	0	Cursor
prefer-assertions-over-defensive-checksprisma/orm	Cursor rule	48k	yesterday	Apache-2.0	A	0	Cursor