meeting-analyzer

meeting-analyzer is an agent for Claude Code, Cursor from gleanwork/cursor-plugins. It costs 21 tokens per session (1,225 once invoked), scanned A, a copy of meeting-analyzer, MIT.

A meeting-search and analysis agent that finds meeting transcripts and extracts decisions, action items, and important discussion points.

In plain words
What is it for?
Use it to find meetings by topic, participant, or time period and summarize what was decided, who is responsible for follow-up, and what mattered in the discussion.
Why use it?
It separates decisions and commitments from topics that were merely discussed, reducing the need to review entire transcripts manually.

Agent for Claude CodeCursor

Written for Cursor and Claude Code: shipped in a Cursor plugin, but also a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Part of the glean plugin — 19 skills, 10 agents, 1 MCP server shipped together

Good fit Use it to find meetings by topic, participant, or time period and summarize what was decided, who is responsible for follow-up, and what mattered in the discussion.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/gleanwork/cursor-plugins/meeting-analyzer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/gleanwork/cursor-plugins

Made for: Claude Code, Cursor.

Or install glean, the plugin that ships this one along with the rest of its 19 skills, 10 agents, 1 MCP server.

Wrote 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.

agentmods badge for meeting-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/agents/gleanwork/cursor-plugins/meeting-analyzer/github.svg)](https://agentmods.dev/agents/gleanwork/cursor-plugins/meeting-analyzer)
Your own site
<a href="https://agentmods.dev/agents/gleanwork/cursor-plugins/meeting-analyzer"><img src="https://agentmods.dev/badge/agents/gleanwork/cursor-plugins/meeting-analyzer/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.

agentmods 80×15 button for meeting-analyzer

Your own site · 80×15
<a href="https://agentmods.dev/agents/gleanwork/cursor-plugins/meeting-analyzer"><img src="https://agentmods.dev/badge/agents/gleanwork/cursor-plugins/meeting-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,225 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.01225
Opus 5.5 $0.00008 $0.00490
Sonnet 5.5 $0.00004 $0.00245
Haiku 4.5 $0.00002 $0.00122

Measured 1mo ago against content hash 395d49fb2829, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

Origin

This is a copy

100% identical to meeting-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.

glean/agents/meeting-analyzer.md · 166 lines

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:

  1. Decisions Made: What was decided? By whom?
  2. Action Items: What tasks were assigned? To whom? By when?
  3. Key Discussion Points: Important topics debated
  4. Open Questions: Unresolved items
  5. 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

Read the full file on GitHub · 166 lines

Changes

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.

  1. 1mo ago First seen · 166 lines · 21 tokens per session scan A 395d49fb2829

Subscribe to this mod's changes

meeting-analyzer is an agent published in the GitHub repository gleanwork/cursor-plugins (4 stars, last pushed 17d ago), licensed MIT. It adds 21 tokens to every session and 1,225 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to meeting-analyzer, differing in 0 lines, and is treated as a copy.