meeting-notes

meeting-notes is a skill for Claude Code, Codex from lvndry/jazz. It costs 33 tokens per session (1,187 once invoked), scanned A, original, MIT.

A tool for turning meeting transcripts, notes, or recordings into a short summary with decisions, owners, and follow-up actions.

In plain words
What is it for?
It helps summarize meetings, extract action items, identify decisions and owners, and draft follow-up emails.
Why use it?
It removes the need to reread a full meeting record to find what was decided and who must act. Missing important context is identified before summarizing.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/lvndry/jazz/meeting-notes
Any agent
npx skills add lvndry/jazz --skill meeting-notes
Clone the repo
git clone --depth 1 https://github.com/lvndry/jazz

Made for: Claude Code, Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/lvndry/jazz/meeting-notes.svg)](https://agentmods.dev/skills/lvndry/jazz/meeting-notes)
Your own site
<a href="https://agentmods.dev/skills/lvndry/jazz/meeting-notes"><img src="https://agentmods.dev/badge/skills/lvndry/jazz/meeting-notes.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,187 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00033 $0.01187
Opus 5 $0.00016 $0.00593
Sonnet 5 $0.00007 $0.00237
Haiku 4.5 $0.00003 $0.00119

Measured 5d ago against content hash bbdab47ae31b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

meeting-notes 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 5d 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.

skills/meeting-notes/SKILL.md · 138 lines

How it starts

The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Meeting Notes

Turn a meeting transcript, pasted notes, or rough draft into a clean summary with explicit decisions, owners, and follow-ups. The goal is one artifact a busy reader can act on in 30 seconds.

When to Use

  • User has meeting notes, a transcript, or a recording and wants a summary
  • User wants action items or follow-ups extracted
  • User asks "what did we decide?" or "what are the next steps?"
  • User wants a follow-up email drafted to attendees

Input Handling

Accept input in any of these forms:

  • Pasted text — transcript, bullet notes, or a rough draft in the conversation
  • File path — if the user gives a path or filename, read it with read_file first; don't ask them to paste a long file
  • Multiple fragments — several messages or files mean one meeting; merge them into a single summary, don't summarize each separately

If something material is missing (which meeting? which date?), ask one targeted question rather than guessing. Don't block on minor unknowns like exact attendee spelling — mark them TBD.

Workflow

  1. Ingest the source (read the file if a path was given).
  2. Summarize in 3–5 sentences: what was discussed, what was decided, the meeting's tone.
  3. Extract decisions — explicit agreements and choices made, with owner/context if stated.
  4. Extract action items — concrete tasks; capture owner and due date when present, else TBD.
  5. Surface open questions, risks, and next-meeting needs so nothing important is buried.
  6. Format the artifact (below) and present it.
  7. Save it if the user wants it kept (see Saving).

Output Format

---
title: [Topic]
date: [YYYY-MM-DD or TBD]
attendees: [Name, Name, … or TBD]
source: [pasted | path/to/file]
tags: [meeting, <project>]
---

# Meeting Summary: [Topic or title]

## Summary
[3–5 sentences: what was discussed, main outcomes, tone of meeting]

## Decisions
- [Decision 1]. [Owner / context if known.]
- [Decision 2]

## Action Items
| Owner  | Action | Due              | Status |
| ------ | ------ | ---------------- | ------ |
| [Name] | [What] | [When if stated] | TBD    |
| …      | …      | …                | …      |

## Open Questions
- [Question or topic to revisit]
- [Blocked item or dependency]

## Risks & Concerns
- [Risk or objection someone raised, briefly]

## Follow-up
- [Next meeting / check-in if scheduled]
- [Item to carry into the next conversation]

Read the full file on GitHub · 138 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. 5d ago First seen · 138 lines · 33 tokens per session scan A bbdab47ae31b

Subscribe to this mod's changes

meeting-notes is a skill published in the GitHub repository lvndry/jazz (51 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 1,187 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.

Related

Other skills, from other repositories

technical-writing

Write, edit, review, or audit user-facing documentation for the eve repository. Use for changes under docs/, documentation tied to eve APIs or CLI behavior, docs work based on Slack or support feedback, and requests to make eve docs clearer, more natural, or less AI-patterned while verifying claims against current…

vercel/eve · 78 tokens

anywrite

Compiled CLI covering all 52 endpoints of the Anytype local API — objects, properties, tags, search, chat, files — one binary, no MCP server needed.

ranbot-ai/awesome-skills · 37 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

generate-run-commands

Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.

microsoft/vscode · 36 tokens

get-search-view-results

Get the current search results from the Search view in VS Code.

microsoft/vscode · 17 tokens

tmux

Remote-control tmux sessions for interactive CLIs by sending keystrokes, capturing pane output, and managing terminal multiplexer windows. Enables parallel coding-agent orchestration, background process management, and REPL interaction via sockets. Use when the agent needs to launch, monitor, or coordinate…

elizaOS/eliza · 87 tokens