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-debriefgit 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-debrief)<a href="https://agentmods.dev/skills/flonat/flonat-research/meetings-debrief"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/meetings-debrief/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-debrief"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/meetings-debrief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 152 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Privilege Escalation · line 190 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00071 | $0.01793 |
| Opus 5 | $0.00036 | $0.00897 |
| Sonnet 5 | $0.00014 | $0.00359 |
| Haiku 4.5 | $0.00007 | $0.00179 |
Grade B, and why
meetings-debrief scanned grade B with 1 finding 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 7d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Set permissions: `chmod 600` How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
meetings-debrief
Post-meeting analysis that reads your latest recording, compares what happened to what you planned, and surfaces decision evolution — so nothing falls through the cracks.
How it works
This is a multi-phase interactive flow. It connects to meetings-prep when a prep file exists, creating a before→after loop.
Phase 1: Find the most recent recording
minutes list --limit 5
Pick the most recent recording. If there are multiple from today, ask via the available structured-question mechanism: "You have [N] recordings today. Which one are you debriefing?" with options listing the titles.
If no recent recording exists:
Say: "I don't see any recent recordings. Did you run minutes record and minutes stop? If the recording is from a specific meeting, tell me the title or date and I'll find it."
Don't proceed without a recording to debrief.
Phase 2: Read the transcript
Use Read on the meeting file path. Extract from the transcript and frontmatter:
- Decisions made (from
decisions:frontmatter or## Decisionssection) - Action items created (from
action_items:frontmatter or## Action Itemssection) - Key discussion points (from
## Summaryor the transcript itself) - Attendees (from
attendees:frontmatter)
Phase 3: Check for matching prep
Look for a prep file that matches this meeting:
ls ~/.minutes/preps/ 2>/dev/null
Match logic:
- Find
.prep.mdfiles from today or yesterday (within 48 hours) - Read each file's
person:frontmatter field - Compare against the recording's
attendees:list — match on first name - If multiple preps match → the available structured-question mechanism to pick which one
- If no prep matches → standalone debrief (skip to 4.2)
Phase 4: Debrief
Two paths depending on whether Phase 3 found a matching prep file.
4.1 Prep-connected debrief (when a matching prep exists)
Read the prep file. Pull out the goal: field. Ask via the available structured-question mechanism:
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.
- 7d ago First seen · 206 lines · 71 tokens per session scan B ec20ddf7ee93
meetings-debrief is a skill published in the GitHub repository flonat/flonat-research (133 stars, last pushed 16d ago), licensed MIT. It adds 71 tokens to every session and 1,793 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
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.
alive:settings
The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…
calendar-event-manager
Create macOS Calendar events with tiered sound alarms and paired Reminders so events are never missed across Mac and iOS.
lark-contact
A Feishu (Lark) contacts tool for finding users or bots and looking up their profiles and contact details.
collection
Choose which SkillNote skill collection is active for this Codex project. Use when the user says "change collection", "switch skills", "use frontend skills", or "show collections".
ask-agents
Send a task or question to Claude Code and/or Gemini as external subagents and report back what they said. Use when the user asks to ask Claude, ask Gemini, ask both, get a second opinion, split reviewer roles, or compare external agents.