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 nimadorostkar/Claude-Skills-collection --skill meeting-notesgit clone --depth 1 https://github.com/nimadorostkar/Claude-Skills-collectionWrote 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/nimadorostkar/claude-skills-collection/meeting-notes)<a href="https://agentmods.dev/skills/nimadorostkar/claude-skills-collection/meeting-notes"><img src="https://agentmods.dev/badge/skills/nimadorostkar/claude-skills-collection/meeting-notes/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/nimadorostkar/claude-skills-collection/meeting-notes"><img src="https://agentmods.dev/badge/skills/nimadorostkar/claude-skills-collection/meeting-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.01157 |
| Opus 5 | $0.00019 | $0.00579 |
| Sonnet 5 | $0.00008 | $0.00231 |
| Haiku 4.5 | $0.00004 | $0.00116 |
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 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Notes
Purpose
Turn a meeting into a record of what was decided and what happens next. A transcript is not notes; nobody reads a transcript, and the value of a meeting evaporates within a week without a record of its decisions.
When to Use
- Summarizing a meeting or a call.
- Processing a transcript or a recording.
- Producing a record of decisions for people who were not there.
- Extracting action items.
Capabilities
- Extracting decisions, actions, and open questions.
- Distinguishing what was decided from what was discussed.
- Attribution and ownership.
- Structuring notes for a reader who was absent.
Inputs
- The transcript, recording, or your own notes.
- The attendees and their roles.
- What the meeting was for.
Outputs
- Decisions, stated with the reasoning.
- Actions with an owner and a date.
- Open questions with an owner.
- Enough context that someone absent can follow.
Workflow
- Extract the decisions first — What was actually decided? Not discussed, not raised, not considered — decided. This is what the meeting produced.
- Extract the actions, with an owner and a date — An action with no owner will not be done. An action with no date will be done eventually, which means never.
- Record the open questions — What was raised and not resolved? These are what the next meeting is for, and they are routinely lost.
- Capture the reasoning behind each decision — Not the whole debate. Why this option, and what was rejected. In six months, the reasoning is the part people need.
- Write for someone who was not there — They have no context. A note that says "agreed to go with Sam's approach" is useless to them and, in two months, to you.
- Send it the same day — Notes sent a week later are archaeology.
Best Practices
- The single most valuable thing in meeting notes is the list of decisions with their reasoning. Everything else is optional.
- An action item without an owner is a wish. Name a person, never a team.
- Do not transcribe the discussion. Nobody reads it, and it obscures the three sentences that matter.
- Record what was rejected and why. It stops the same option being re-proposed at the next meeting.
- If nothing was decided, say so plainly. A meeting that produced no decision is worth knowing about.
- Circulate the notes and invite corrections. The record everyone has seen and not disputed is a stronger record than the one you wrote alone.
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 · 111 lines · 38 tokens per session scan A dc6a8991f47d
meeting-notes is a skill published in the GitHub repository nimadorostkar/Claude-Skills-collection (26 stars, last pushed 25d ago), licensed MIT. It adds 38 tokens to every session and 1,157 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
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
implement-improvements
Validate improvements from .turbo/improvements.md, recommend a working set tailored to what's in the backlog, and run one lane: direct fixes, investigation, or planned work. One lane per session. Use when the user asks to "implement improvements", "work on improvements", "address improvements", "process improvement…
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
create-issue
Create a GitHub issue with a drafted title and body. Use when the user asks to "create an issue", "file an issue", "open an issue", "submit an issue", "report a bug", "file a bug report", "file a feature request", or "file a design proposal".
pick-next-issue
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".