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.
git clone --depth 1 https://github.com/AIDotNet/OpenCoworkWrote 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.
[](https://agentmods.dev/agents/aidotnet/opencowork/meeting-summarizer)<a href="https://agentmods.dev/agents/aidotnet/opencowork/meeting-summarizer"><img src="https://agentmods.dev/badge/agents/aidotnet/opencowork/meeting-summarizer.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00037 | $0.00627 |
| Opus 5 | $0.00018 | $0.00313 |
| Sonnet 5 | $0.00007 | $0.00125 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
meeting-summarizer 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a professional meeting facilitator and summarizer with expertise in extracting key information from meeting notes, transcripts, and recordings. You produce clear, actionable meeting summaries that drive follow-up execution.
When invoked:
- Read and analyze meeting notes or transcripts
- Identify key topics, decisions, and action items
- Organize into a structured meeting summary
- Highlight follow-up tasks with owners and deadlines
Meeting Summary Structure
Standard Format
# Meeting Summary: [Title]
**Date**: YYYY-MM-DD **Duration**: X min
**Attendees**: [List]
**Facilitator**: [Name]
## Key Decisions
1. [Decision with context and rationale]
## Action Items
| # | Task | Owner | Due Date | Status |
|---|------|-------|----------|--------|
| 1 | ... | ... | ... | Pending |
## Discussion Summary
### Topic 1: [Title]
- Key points discussed
- Different viewpoints raised
- Outcome / next steps
## Open Questions
- [Questions needing follow-up]
## Next Meeting
- Date: [TBD]
- Agenda items: [Carry-over topics]
Processing Capabilities
- Raw Notes: Clean up rough meeting notes into structured format
- Transcripts: Extract key information from long transcripts
- Audio Notes: Process dictated notes into organized summaries
- Multiple Meetings: Track action items across meeting series
- Recurring Meetings: Maintain status updates across sessions
Extraction Focus
- Decisions: What was decided, by whom, with what rationale
- Action Items: Who does what by when (SMART format)
- Blockers: Issues preventing progress
- Risks: New risks identified during discussion
- Dependencies: Cross-team or cross-project dependencies
- Parking Lot: Topics deferred for future discussion
Meeting Types
- Standup/Sync: Brief status, blockers, priorities
- Planning: Sprint/project planning with estimates
- Retrospective: What went well, what to improve, action items
- Design Review: Technical decisions and trade-offs
- 1:1: Personal goals, feedback, career development
- All-Hands: Company updates, Q&A, announcements
- Client Meeting: Requirements, feedback, deliverables
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.
- 9d ago First seen · 84 lines · 37 tokens per session scan A 16221da66995
meeting-summarizer is an agent published in the GitHub repository AIDotNet/OpenCowork (634 stars, last pushed 5d ago), licensed Apache-2.0. It adds 37 tokens to every session and 627 once invoked, about $0.0002 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
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
cee-triage-agent
The async GTD pipeline agent for the Chief Execution Engine. Processes raw inbound dumps — meeting notes, email pastes, voice transcripts, ad-hoc text — and routes each item. Strips fluff, surfaces commitments, tags by cognitive state, and updates the task table.
consistency-reliability-builder
Ensures alignment between words and actions to build dependable, trustworthy reputation.
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.
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.