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 charlie947/life-automation-skills --skill meeting-notesgit clone --depth 1 https://github.com/charlie947/life-automation-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/charlie947/life-automation-skills/meeting-notes)<a href="https://agentmods.dev/skills/charlie947/life-automation-skills/meeting-notes"><img src="https://agentmods.dev/badge/skills/charlie947/life-automation-skills/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/charlie947/life-automation-skills/meeting-notes"><img src="https://agentmods.dev/badge/skills/charlie947/life-automation-skills/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.00138 | $0.01721 |
| Opus 5 | $0.00069 | $0.00860 |
| Sonnet 5 | $0.00028 | $0.00344 |
| Haiku 4.5 | $0.00014 | $0.00172 |
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 12d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use this skill
Use it when the user wants a meeting turned into a summary and a set of tracked action items:
- "Summarise my meeting" / "recap the call" / "write up that meeting"
- "What did we decide?" / "what were the action items from that call?"
- "Meeting notes for the sync" / "send me the notes"
- Any request to capture a call and route the follow-ups into a task system.
Do not use it to invent notes for a meeting the connector cannot find, to assign an owner or a due date the record does not support, or to write to Notion before the user has seen and approved the action list.
What it needs (setup)
A read source for the meeting, plus a write target for the output.
- Granola connector (read). Pulls your meetings, transcripts, and Granola's own AI notes. It is read-only. It gives you what was said and Granola's write-up. It does not hand you structured owners or due dates. Those live inside the conversation, and you extract them from the words.
- Fireflies (read, via the Zapier connector). Fireflies is reached through Zapier, not a native connector. The Zapier action finds a meeting and returns Fireflies' summary and action items as Fireflies generated them, plus a transcript where the action exposes one. Field coverage is fixed by the Zapier action. Treat anything the action does not return as missing, never as something to fill in.
- Notion connector (write). Creates the summary page and one task row per action item. It needs a target: an existing page to nest the summary under, and a database (or list) to hold the tasks. If the user has not named one, ask. Do not create workspace structure blind.
If the read source is not connected, tell the user which one to enable and stop. Do not guess or fabricate the meeting.
The limit to design around: transcription tools capture words, not accountability. Neither Granola nor Fireflies exposes owners and due dates as clean structured fields. So this skill reads what was actually said, proposes owners and dates only where the record supports them, marks every gap, and confirms the full list with the user before a single row lands in Notion.
What ships with it
1 file 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.
- 12d ago First seen · 86 lines · 0 tokens per session scan A 7232de5271cb
meeting-notes is a skill published in the GitHub repository charlie947/life-automation-skills (23 stars, last pushed 14d ago), licensed MIT. It adds 138 tokens to every session and 1,721 once invoked, about $0.0007 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.