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 codebygarv/Ai-skills --skill meeting-notes-distillergit clone --depth 1 https://github.com/codebygarv/Ai-skillsWrote 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/codebygarv/ai-skills/meeting-notes-distiller)<a href="https://agentmods.dev/skills/codebygarv/ai-skills/meeting-notes-distiller"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/meeting-notes-distiller/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/codebygarv/ai-skills/meeting-notes-distiller"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/meeting-notes-distiller.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.00038 | $0.00437 |
| Opus 5 | $0.00019 | $0.00218 |
| Sonnet 5 | $0.00008 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
meeting-notes-distiller 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.
What it actually says
Purpose
Convert raw, unstructured meeting notes or a transcript into a clean summary of what was decided and what needs to happen next — the artifact people actually reread, instead of scrolling back through a wall of raw notes.
When to Use
- A meeting just happened and raw notes/transcript exist that need to become a shareable summary.
- Someone missed a meeting and needs to catch up without reading the full transcript.
- A recurring meeting needs a consistent summary format over time.
What to Analyze / Do
- Separate discussion from decisions — most of a meeting is discussion; only some of it results in an actual decision. Distinguish clearly between "this was debated" and "this was decided."
- Extract action items — each with an owner if stated or clearly implied, and a deadline if one was mentioned; mark "owner unclear" rather than guessing.
- Note open questions — things that were raised but not resolved, so they don't silently disappear.
- Preserve important context/rationale for non-obvious decisions — "we chose X" is less useful than "we chose X because Y consideration outweighed Z," when that reasoning was actually discussed.
- Keep it short — a meeting summary that's nearly as long as the transcript defeats the purpose.
Output Format
- Decisions — bullet list, each a clear, standalone statement.
- Action Items — table: Action | Owner | Deadline (if any).
- Open Questions — bullet list of unresolved items.
- Optional Context section for decisions that need a brief "why," only when genuinely useful.
Avoid
- Padding with a full chronological recap of everything discussed — summarize outcomes, don't transcribe.
- Inventing an owner or deadline that wasn't actually stated or clearly implied.
- Losing genuinely important dissenting opinions or open questions in service of a tidy-looking summary.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 36 lines · 38 tokens per session scan A 4586daa8eaa6
meeting-notes-distiller is a skill published in the GitHub repository codebygarv/Ai-skills (25 stars, last pushed 20d ago), licensed MIT. It adds 38 tokens to every session and 437 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 skills, from other repositories
git-project
GitHub Projects (v2) setup and management via gh CLI + GraphQL: organize a repo's issues into epics with native sub-issues, drive a board Status flow (Todo -> In Progress -> Done), set Project Priority, classify with native issue Types (Task/Bug/Feature) instead of labels, scope work with milestones (incl. resolving…
bun-api
Bun runtime API reference for TypeScript scripts. Covers Bun.serve() HTTP/HTTP/2 server with routes and WebSockets, fetch() transport options, Bun.file(), Bun.write(), Bun.$() shell, Bun.spawn(), Bun.Glob, Bun.env, bun:sqlite, Bun.sql() for PostgreSQL/MySQL via DATABASEURL, Bun.s3 for S3-compatible storage, Bun.redis…
bun-cli
Bun CLI reference for package management, script running, testing, bundling, and compilation. Covers bun install/add/remove/update, bun run, bun test, bun build, bunx, bun patch, bun audit fix, bun dedupe, bun prune, bun why, bun pm, bun repl, bunfig.toml, bun.lock, workspace catalogs, isolated installs and the global…
deps-upgrade
Validate JavaScript/TypeScript dependency upgrades after an interactive or manual update. Establish the real delta from git, detect peer/engine/type conflicts, extract breaking changes, migrations and adoptable features from release notes, assess held-back or seemingly unused packages, and run verification gates.…
git-pr
PR and MR workflows for GitHub (gh) and GitLab (glab). Creation, review comment handling, thread resolution, review state queries, merging, cost-aware bot review rounds (GitHub: Copilot, CodeRabbit), and Copilot code review configuration (rulesets, custom instructions, billing). Use when creating PRs/MRs, addressing…
git-ci
CI/CD status queries for GitHub Actions (gh) and GitLab CI (glab). Check pipeline status, failing jobs, workflow runs, job logs, and merge readiness. Use when checking CI status, debugging build failures, viewing job logs, watching pipeline progress, or configuring gh/glab CI read-only allowlists. Not for PR workflows…