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/claude-plugins/using-glean-productivitynpx skills add gleanwork/claude-plugins --skill using-glean-productivitygit clone --depth 1 https://github.com/gleanwork/claude-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- using-glean-productivity — 100% identical, 0 lines differ
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/claude-plugins (25 stars, last pushed 13d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
lark-im
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
reflect
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
organize-threads
猫猫辅助整理未分类 thread，分析标题和元数据，建议合适的标签。 Use when: 用户说"帮我整理"、"分类 thread"、点击整理按钮。 Not for: 删除/编辑标签本身。 Output: 按 thread 的标签建议列表。.