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 liqiongyu/lenny_skills_plus --skill running-effective-meetingsgit clone --depth 1 https://github.com/liqiongyu/lenny_skills_plusWrote 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/liqiongyu/lenny_skills_plus/running-effective-meetings)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/running-effective-meetings"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/running-effective-meetings/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/liqiongyu/lenny_skills_plus/running-effective-meetings"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/running-effective-meetings.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.00044 | $0.02028 |
| Opus 5 | $0.00022 | $0.01014 |
| Sonnet 5 | $0.00009 | $0.00406 |
| Haiku 4.5 | $0.00004 | $0.00203 |
Grade A, and why
running-effective-meetings 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running Effective Meetings
Scope
Covers
- Deciding whether a meeting is needed (vs async doc/message)
- Choosing the right meeting format (operational / strategic / decision / workshop)
- Preparing a pre-read and “priming” to avoid context-less discussions
- Facilitating discussion, capturing decisions, and ensuring follow-through
- Improving recurring meeting hygiene (split/kill/shorten meetings)
When to use
- “Create an agenda and facilitation plan for a decision meeting.”
- “We need a weekly operational cadence — design the meeting format and templates.”
- “This meeting keeps going in circles — redesign it so we decide and assign actions.”
- “Turn this messy invite into a clear meeting brief + pre-read + follow-up.”
When NOT to use
- The goal is purely status updates (use async updates instead).
- There is no discussion to be had (you already have the decision and only need to broadcast it).
- The “decision owner” is not attending and cannot delegate decision rights.
- You need a recurring 1:1 with a direct report or manager (use
running-effective-1-1s; different structure and relationship dynamics). - You need a multi-day offsite or retreat (use
running-offsites; this skill covers single meetings, not multi-session programs). - You need a formal decision process with RACI, options scoring, and escalation (use
running-decision-processes; this skill captures decisions within meetings but does not design the full decision framework). - You need a design review or architecture review with technical critique (use
running-design-reviews; specialized facilitation and feedback norms apply). - The topic is a sensitive HR/legal/medical issue requiring specialist handling.
Inputs
Minimum required
- Meeting objective (what changes after the meeting)
- Meeting type (or “recommend”): operational / strategic discussion / decision / workshop
- Attendees (and the decision owner, if any)
- Time box + date/time constraints (and remote/hybrid details)
- Context links or a 5–10 bullet background summary
What ships with it
13 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.
- eval/eval_config.json 1.5 KB
- eval/SHOWCASE.md 5.3 KB
- eval/with_skill.md 29 KB
- eval/without_skill.md 20 KB
- README.md 993 B
- references/CHECKLISTS.md 1.7 KB
- references/EXAMPLES.md 1.3 KB
- references/INTAKE.md 1.4 KB
- references/RUBRIC.md 3.9 KB
- references/SOURCE_SUMMARY.md 2.3 KB
- references/TEMPLATES.md 3.0 KB
- references/WORKFLOW.md 3.5 KB
- skillpack.json 397 B
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 · 141 lines · 44 tokens per session scan A 98b01b8d6510
running-effective-meetings is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (52 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 2,028 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-09-03.
Other skills, from other repositories
exec-weekly-agenda-generator
Synthesize the past week across meetings, chat, email, and calendar to generate a ranked list of 5-10 topics for the weekly leadership team meeting. Use when the user asks to prep for their leadership meeting, generate meeting topics, build the agenda, or says "prep me for Monday.".
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
recipe-plan-weekly-schedule
Review your Google Calendar week, identify gaps, and add events to fill them.
recipe-review-overdue-tasks
Find Google Tasks that are past due and need attention.