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 skills add gleanwork/cursor-plugins --skill using-gleangit 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/skills/gleanwork/cursor-plugins/using-glean)<a href="https://agentmods.dev/skills/gleanwork/cursor-plugins/using-glean"><img src="https://agentmods.dev/badge/skills/gleanwork/cursor-plugins/using-glean/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/skills/gleanwork/cursor-plugins/using-glean"><img src="https://agentmods.dev/badge/skills/gleanwork/cursor-plugins/using-glean.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.00171 | $0.01148 |
| Opus 5.5 | $0.00068 | $0.00459 |
| Sonnet 5.5 | $0.00034 | $0.00230 |
| Haiku 4.5 | $0.00017 | $0.00115 |
Grade A, and why
using-glean 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.
This is a copy
100% identical to using-glean — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Glean
The Glean MCP server exposes a family of tools that let the assistant query the user's company knowledge: documents, people, meetings, email, internal code, the user's activity feed, structured memory, and the knowledge graph. This skill is the entry point. It maps a user's question to the right tool, names the rules that apply across all of them, and links to per-tool reference files that carry the deep syntax.
Where these tools live
The tools listed below come from the user's Glean MCP server connection. Refer to them by their bare names (search, employee_search, meeting_lookup, …) — the assistant resolves them against the active tool inventory.
In the raw MCP tool list, Glean tools appear as mcp__glean_[server-name]__[tool] where [server-name] is the user's configured server identifier (e.g., default, production, acme). The tool suffix after the final __ is always consistent across deployments. Use whatever Glean server is visible in your tool inventory.
If no Glean tools are visible, ask the user to set up Glean by prompting the
harness (for example, Set up Glean for me).
Intent → tool decision tree
| The user is asking about... | Reach for | Reference |
|---|---|---|
| Documents, wikis, policies, RFCs, specs | search |
search.md |
| A complex question that needs synthesis across sources | chat |
chat.md |
| Internal source code, files, commits across repos | code_search |
code-search.md |
| People, teams, org structure, reporting lines | employee_search |
employee-search.md |
| Meetings, transcripts, decisions, action items | meeting_lookup |
meeting-lookup.md |
| Gmail messages, threads, attachments | gmail_search |
gmail-search.md |
| Outlook messages, threads, attachments | outlook_search |
outlook-search.md |
| Reading a specific URL / document | read_document |
read-document.md |
| The user's own recent activity (standup, weekly summary) | user_activity |
user-activity.md |
| The user's stored memories / personalization | memory (+ memory_schema) |
memory.md |
| Structured entity / relationship queries | knowledge_graph_query (+ knowledge_graph_schema) |
knowledge-graph.md |
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- reference/agents-as-tools.md 3.3 KB
- reference/chat.md 2.4 KB
- reference/code-search.md 2.8 KB
- reference/employee-search.md 3.7 KB
- reference/gmail-search.md 2.2 KB
- reference/knowledge-graph.md 3.8 KB
- reference/meeting-lookup.md 4.2 KB
- reference/memory.md 7.1 KB
- reference/outlook-search.md 2.3 KB
- reference/read-document.md 2.5 KB
- reference/search.md 5.3 KB
- reference/synthesis.md 4.8 KB
- reference/user-activity.md 2.4 KB
- reference/vetting.md 5.0 KB
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 · 55 lines · 171 tokens per session scan A 52fc10fd21d6
using-glean is a skill published in the GitHub repository gleanwork/cursor-plugins (4 stars, last pushed 17d ago), licensed MIT. It adds 171 tokens to every session and 1,148 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to using-glean, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
baoyu-youtube-transcript
A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Fetches URLs and PDFs, then summarizes or returns clean Markdown. Use when asked to read, fetch, quote, cite, convert, or save a URL or PDF. Not for local text files already in the repo.