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 ericrisco/rsc-harness --skill meeting-notesgit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/meeting-notes)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/meeting-notes"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/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/ericrisco/rsc-harness/meeting-notes"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/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.00082 | $0.02990 |
| Opus 5.5 | $0.00033 | $0.01196 |
| Sonnet 5.5 | $0.00016 | $0.00598 |
| Haiku 4.5 | $0.00008 | $0.00299 |
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 1mo 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Notes — Make the Meeting Count
The meeting just ended. Pull the decisions and the why, assign the actions with owners and real dates, flag what's still open, and ship a record someone who missed it can act on.
You own the point-in-time meeting record: take a transcript or raw notes, separate signal from noise, and emit a curated artifact — decisions (with rationale), action items (owner + due date), open questions, and a one-screen TL;DR. The output is human-readable judgment, not a code file.
Not this skill
| If the ask is… | Route to |
|---|---|
| The durable decision record — full rationale, alternatives weighed, reversibility argued, review cadence | decision-records. This skill captures a decision in its meeting context and hands the heavy ADR off; it does not maintain the long-lived artifact |
| A reusable step-by-step procedure / runbook | sop-builder. A SOP is a repeatable how-to; meeting notes are a point-in-time record |
| Tracking the emitted tasks across a board / sprint | project-ops. This skill emits action items; their lifecycle is not its job |
| Scheduling the meeting, finding a slot, sending the invite | calendar-scheduling |
| Building the integration that pushes notes into Notion/Slack/a tracker | notion-connector / automation-flows |
| Summarizing an arbitrary document that is not a meeting | document-processing |
The capture loop
This is the spine. Six steps, in order:
- Consent & setup — if it's being recorded, announce it and get consent before capture (see Consent below). Note attendees, date, purpose.
- Capture in real time — record context → decision → action as the discussion happens. Don't reconstruct from memory hours later; you'll lose the why and invent the rest. (Umbrex, accessed 2026-06-02.)
- Sort signal from noise — a useful record filters to decisions, commitments, and open questions. It is not a transcript. (Fellow.app / VoiceType, accessed 2026-06-02.)
- Extract decisions + actions + open questions — into the skeleton below.
- Verify — confirm each owner accepts their task while everyone is still present. For AI drafts this step is mandatory and heavier (see Working with AI transcripts).
- Ship the recap within 24–48h — as a draft, invite corrections, then finalize. (VoiceType / Wrike, accessed 2026-06-02.)
What ships with it
3 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.
- 1mo ago First seen · 154 lines · 82 tokens per session scan A 6a97c5ee4d4f
meeting-notes is a skill published in the GitHub repository ericrisco/rsc-harness (267 stars, last pushed 2d ago), licensed MIT. It adds 82 tokens to every session and 2,990 once invoked, about $0.0003 per session on Opus 5.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
dev-document
Code that generates documents inside an application (PDF, DOCX, XLSX, PPTX) - choose and wire the library for an export endpoint, an invoice, a scheduled report. Trigger when the user wants their app or a script to generate, export or download PDF/Word/Excel/PowerPoint files. For Claude itself to write, read or edit…
doc-generate
Technical documentation generation. Trigger when the user wants to create a README, API docs, or guides.
clean-messy-notes-to-action-items
Turn unstructured notes into action items with owners, deadlines, decisions, and unresolved follow-ups.
extract-facts
Extracts Service/Incident/Cause facts from an incident-report document against a fixed schema, rejecting anything the schema doesn't define.
meeting-notes
Turn meeting transcripts or voice recordings into structured notes with action items, decisions, and owners. Use when the user shares a transcript, meeting recording, or asks to summarize a meeting. Triggers on: "meeting notes", "summarize this meeting", "action items from", "what was decided", "meeting summary"…
slidev-multi-agent
Create, edit, theme, build, and export Slidev presentations using a script-first workflow with detailed local references. Use when working on Slidev decks, themes, layouts, exports, or hosting. Always consult references/index.md first and execute via scripts when available.