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 flonat/flonat-research --skill meetings-weeklygit clone --depth 1 https://github.com/flonat/flonat-researchWrote 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/flonat/flonat-research/meetings-weekly)<a href="https://agentmods.dev/skills/flonat/flonat-research/meetings-weekly"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/meetings-weekly/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/flonat/flonat-research/meetings-weekly"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/meetings-weekly.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.00069 | $0.01489 |
| Opus 5 | $0.00034 | $0.00745 |
| Sonnet 5 | $0.00014 | $0.00298 |
| Haiku 4.5 | $0.00007 | $0.00149 |
Grade A, and why
meetings-weekly 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
meetings-weekly
Synthesize an entire week of meetings and voice memos into a forward-looking brief — themes, decision arcs, stale commitments, and what deserves attention Monday.
How it works
This is a synthesis skill, not a command wrapper. It reads across all meetings, cross-references decisions and action items, and produces an intelligence brief.
Phase 1: Gather this week's recordings
minutes list --limit 50
Filter to recordings from the last 7 days by checking the date field in each result's frontmatter. Do NOT use minutes search with a date string as the query — that searches file content, not dates.
For each recording from the past 7 days, read the full file with Read to get content.
If zero recordings this week: Say: "No recordings found for the past 7 days. Nothing to synthesize." Offer: "Want me to look at the past 2 weeks instead?" Do NOT hallucinate a weekly summary.
If only 1-2 recordings: Still produce the brief — it's shorter but still valuable. Note: "Light week — only [N] recordings."
Phase 2: Theme extraction
Identify the 3-5 dominant themes across all meetings this week. A theme is a topic that appeared in 2+ meetings.
For each theme:
- Which meetings discussed it
- How the conversation evolved across meetings
- Whether a resolution was reached
Present as:
## This Week's Themes
### 1. Pricing (3 meetings)
- Mon: Case proposed $599 baseline
- Wed: Alex pushed back to annual billing
- Fri: Agreed on monthly billing experiment
- Status: RESOLVED (after 3 discussions)
### 2. Q2 Roadmap (2 meetings)
- Tue: Committed to April ship date
- Thu: Discussed pushing to May
- Status: CONFLICTING — not reconciled
Phase 3: Decision evolution arcs
For every decision made this week, search for prior decisions on the same topic in the last 30 days:
minutes search "<topic>" --since <30-days-ago> --limit 20
Classify each decision:
- STABLE — Decision held across 2+ mentions → "Locked in"
- VOLATILE — Changed 2+ times in 14 days → "Still in flux"
- CONFLICTING — Two active contradictory decisions → "Needs reconciliation"
- NEW — First time this topic was decided → "Fresh"
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 · 163 lines · 69 tokens per session scan A bf68c54709e3
meetings-weekly is a skill published in the GitHub repository flonat/flonat-research (133 stars, last pushed 17d ago), licensed MIT. It adds 69 tokens to every session and 1,489 once invoked, about $0.0003 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
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
lark-workflow-standup-report
A workflow that combines calendar events with unfinished Lark tasks to produce a daily or weekly work summary.
dev-companion
WHAT — Dev Companion (general): layered companion for client delivery; modes, gates, delegation to assistant and workflow-generic-project; no CLI matrices.
done
Wrap up the current session by writing a short HANDOFF.md in the project folder, so the next session can resume quickly. Use when the user says done, wrap up, close this out, or capture the session.
daily-brief
Surfaces recent updates relevant to you from GitHub, Linear, Slack, and other configured sources — PR reviews, new assignments, ticket changes, mentions, and CI failures. Use when starting work, catching up after being away, or prepping for standup.
recipe-block-focus-time
Create recurring focus time blocks on Google Calendar to protect deep work hours.