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 skills/gleanwork/cursor-plugins/using-glean-productivitynpx skills add gleanwork/cursor-plugins --skill using-glean-productivitygit 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.00152 | $0.00777 |
| Opus 5 | $0.00076 | $0.00388 |
| Sonnet 5 | $0.00030 | $0.00155 |
| Haiku 4.5 | $0.00015 | $0.00078 |
Grade A, and why
using-glean-productivity 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.
This is a copy
100% identical to using-glean-productivity — 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Glean for Personal Productivity
This skill drives queries about the user's own work life — their recent activity, what they accomplished, what's pending, what's urgent. It pulls from user_activity, meeting_lookup, search (with from:me / owner:me), and memory to assemble a personal view rather than an enterprise-wide one.
Two shapes of question
Most personal-productivity asks fall into two shapes:
- Activity / accomplishments — "what did I work on?", "summarize my week", "what shipped?". See reference/activity.md.
- Priorities / blockers — "what's urgent?", "what needs my attention?", "what's waiting on me?". See reference/priorities.md.
The two overlap (a recent activity feed is the substrate for triaging priorities), but the output the user wants is different: activity is retrospective, priorities are prospective.
Tool reference lives in using-glean
user_activity, memory, search, and meeting_lookup are documented canonically in the using-glean skill:
../using-glean/reference/user-activity.md— date-range mechanics, the inclusive/exclusive end-date pitfall../using-glean/reference/memory.md—memory+memory_schemafor personalization../using-glean/reference/search.md— for documents the user authored or was mentioned in../using-glean/reference/meeting-lookup.md— for meetings the user attended
This skill carries the workflow on top.
Cross-cutting rules
- Quality over volume. A status update of 5 real accomplishments beats a list of 20 trivial activities. Filter aggressively per reference/activity.md.
- Distinguish "did" from "viewed".
user_activityreturns both. Surface creates / edits / decisions; demote pure views. - Cite sources. Every claim should link back to a doc, meeting, or commit so the user can verify and dig deeper.
- Personalize via memory. When framing a summary,
memory(especiallyRolesAndResponsibilitiesandActiveProjects) tells you what themes the user thinks they work on. Group by those themes when possible. - Apply vetting. Even self-activity should be filtered. See
../using-glean/reference/vetting.md.
What ships with it
2 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.
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 · 42 lines · 152 tokens per session scan A 565f4dffed3e
using-glean-productivity is a skill published in the GitHub repository gleanwork/cursor-plugins (4 stars, last pushed 12d ago), licensed MIT. It adds 152 tokens to every session and 777 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to using-glean-productivity, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…