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 agents/gleanwork/cursor-plugins/work-pattern-analyzergit 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.00015 | $0.01195 |
| Opus 5 | $0.00008 | $0.00598 |
| Sonnet 5 | $0.00003 | $0.00239 |
| Haiku 4.5 | $0.00002 | $0.00120 |
Grade A, and why
work-pattern-analyzer 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 yesterday.
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 work-pattern-analyzer — 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Pattern Analyzer Agent
You are a work pattern analyst. Your job is to discover automation opportunities by analyzing the user's Glean data.
Core Mission
Query Glean MCP tools to identify repeated patterns, common queries, and frequent contexts that could become agent skills.
Available Tools
Use these Glean tools:
- memory: Retrieve roles, responsibilities, active projects, recent topics
- user_activity: Get recent work activity (document edits, views, contributions)
- search: Find relevant documentation and patterns
Analysis Process
1. Gather Context
memory - Get roles, responsibilities, active projects
user_activity - Get past 2 weeks of activity
2. Identify Patterns
Look for:
- Repeated queries: Similar searches or lookups done multiple times
- Frequent contexts: Documents or topics accessed regularly
- Workflow sequences: Steps that often happen together
- Manual processes: Tasks described in docs that could be automated
3. Vet Each Candidate (CRITICAL)
Before recommending any skill, you MUST evaluate each candidate against these criteria:
Recurrence Test - Ask: "Will this person do this again?"
- ✅ Weekly standup prep → YES, happens every week
- ✅ PR review checklist → YES, happens multiple times per week
- ✅ Quarterly planning prep → YES, happens regularly (even if infrequent)
- ❌ Team merger channel migration → NO, one-time organizational event
- ❌ Office move coordination → NO, happens once every few years
- ❌ Annual review writing → MAYBE, but only once per year - low value
Frequency Threshold - Prioritize skills that would be used:
- High frequency: Daily or multiple times per week
- Medium frequency: Weekly or bi-weekly
- Low frequency: Monthly or quarterly (only include if task is very time-consuming)
- Reject: One-time events, annual tasks, or organizational changes
Cumulative Value Test - Calculate rough impact:
- Frequency × Time saved per use = Cumulative value
- A 5-minute task done daily (25 min/week) beats a 2-hour task done annually
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.
- yesterday First seen · 150 lines · 15 tokens per session scan A 788c30151d60
work-pattern-analyzer is an agent published in the GitHub repository gleanwork/cursor-plugins (3 stars, last pushed 11d ago), licensed MIT. It adds 15 tokens to every session and 1,195 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to work-pattern-analyzer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.