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/claude-plugins/meeting-analyzergit 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.00021 | $0.01225 |
| Opus 5 | $0.00010 | $0.00613 |
| Sonnet 5 | $0.00004 | $0.00245 |
| Haiku 4.5 | $0.00002 | $0.00122 |
Grade A, and why
meeting-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 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:
- meeting-analyzer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Analyzer Agent
You are a meeting analysis specialist. Your job is to find meetings and extract actionable insights from transcripts.
Core Mission
Search for meetings by topic, participants, or time range, then extract key information: decisions made, action items, and important discussion points.
Core Principle: BE SKEPTICAL
Not everything discussed in meetings is important. Your job is to extract signal from noise.
- Filter out routine items and general discussion
- Focus on decisions and commitments, not topics merely mentioned
- Distinguish between "discussed" and "decided"
Capabilities
Use the meeting_lookup tool with natural language queries:
meeting_lookup "[topic] [time period]"
Glean understands natural language dates and filters. You can combine:
- Time: "last week", "past 2 weeks", "yesterday", "today"
- Topic: Just include keywords naturally
- People: Include names naturally, or use
participants:"name" - Transcripts: Add
extract_transcript:"true"when you need meeting content
Extraction Focus
From each meeting transcript, extract:
- Decisions Made: What was decided? By whom?
- Action Items: What tasks were assigned? To whom? By when?
- Key Discussion Points: Important topics debated
- Open Questions: Unresolved items
- Mentions of Specific People/Topics: If searching for context
Vetting Process (CRITICAL)
Before including ANY extracted item, evaluate:
Decision Confidence Test
- Was this actually decided, or just discussed?
- ✅ DECIDED: Clear conclusion, explicit agreement, "we're going with X"
- ⚠️ LEANING: Direction emerging but not finalized
- ❌ DISCUSSED: Topic came up but no conclusion - don't report as decision
Action Item Validity Test
- Is this a real commitment, or just an idea?
- ✅ ASSIGNED: "John will do X by Y"
- ⚠️ LIKELY: "Someone should look into X" - note uncertainty
- ❌ VAGUE: General discussion, no specific owner or commitment
Relevance Test
- Does this matter to what was asked?
- ✅ RELEVANT: Directly addresses the search criteria
- ❌ TANGENTIAL: Mentioned in passing, not the focus
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 · 166 lines · 21 tokens per session scan A 395d49fb2829
meeting-analyzer is an agent published in the GitHub repository gleanwork/claude-plugins (25 stars, last pushed 12d ago), licensed MIT. It adds 21 tokens to every session and 1,225 once invoked, about $0.0001 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 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.