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 skills add tomzx/agents --skill summarize-meetinggit clone --depth 1 https://github.com/tomzx/agentsWrote 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/skills/tomzx/agents/summarize-meeting)<a href="https://agentmods.dev/skills/tomzx/agents/summarize-meeting"><img src="https://agentmods.dev/badge/skills/tomzx/agents/summarize-meeting/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.
<a href="https://agentmods.dev/skills/tomzx/agents/summarize-meeting"><img src="https://agentmods.dev/badge/skills/tomzx/agents/summarize-meeting.svg" alt="Reviewed on agentmods" width="80" 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.00047 | $0.00883 |
| Opus 5 | $0.00023 | $0.00441 |
| Sonnet 5 | $0.00009 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
summarize-meeting 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 7d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summarize Meeting
Reads a meeting transcript file and produces a structured summary covering key topics, decisions, action items, owners, and open questions.
Prerequisites
- A transcript file (markdown, plain text, or any readable text format) provided by the user
- If no file path is provided, stop and ask the user to supply one
Steps
- Read the full transcript file provided by the user.
- Identify meeting participants from the transcript (speakers, attendees mentioned).
- Extract the main topics discussed, preserving chronological order where it aids comprehension.
- For each topic, summarize the discussion in 1-3 sentences capturing the key points.
- Identify all explicit decisions made during the meeting (decisions with clear consensus or sign-off).
- Extract all action items with assigned owners and deadlines where mentioned.
- List any open questions, unresolved issues, or items deferred to future meetings.
- Write the output to a file named
<transcript-stem>-summary.mdin the same directory as the input transcript (e.g.,transcript.mdbecomestranscript-summary.md).
Output Format
# Meeting Summary: <Title or Topic>
**Date:** <date if mentioned, otherwise "Not specified">
**Duration:** <duration if mentioned, otherwise "Not specified">
**Participants:** <comma-separated list of names/identifiers>
---
## Topics Discussed
### <Topic 1>
<1-3 sentence summary of the discussion on this topic.>
### <Topic 2>
<1-3 sentence summary of the discussion on this topic.>
## Decisions
- **<Decision 1>:** <brief context or rationale>
- **<Decision 2>:** <brief context or rationale>
## Action Items
| Action | Owner | Deadline |
|---|---|---|
| <What needs to be done> | <Who> | <When, or "Not specified"> |
## Open Questions
- <Question or unresolved issue 1>
- <Question or unresolved issue 2>
## Key Quotes (optional)
> "<Notable or important quote>" — <Speaker>
> "<Notable or important quote>" — <Speaker>
Only include this section if there are quotes that capture important decisions, commitments, or insights not easily paraphrased.
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.
- 7d ago First seen · 99 lines · 47 tokens per session scan A 41cf77a03e0a
summarize-meeting is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 883 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.