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 alivirgo/Major-AI-Skills --skill draft-meeting-agendasgit clone --depth 1 https://github.com/alivirgo/Major-AI-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/alivirgo/major-ai-skills/draft-meeting-agendas)<a href="https://agentmods.dev/skills/alivirgo/major-ai-skills/draft-meeting-agendas"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/draft-meeting-agendas/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/alivirgo/major-ai-skills/draft-meeting-agendas"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/draft-meeting-agendas.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.00027 | $0.01130 |
| Opus 5.5 | $0.00011 | $0.00452 |
| Sonnet 5.5 | $0.00005 | $0.00226 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
draft-meeting-agendas 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft Outcome-Driven Meeting Agendas (Time-Blocked Agenda) (AI Skill)
Overview
Unstructured meetings without a defined objective or time allocations almost always expand to fill their scheduled duration (Parkinson's Law), devolving into unfocused discussion without clear decisions.
The Outcome-Driven Agenda Protocol forces the AI to structure meetings around a Single Primary Decision, time-boxing each topic in 5-to-10 minute increments with assigned discussion leads and mandatory pre-read links.
The Outcome-Driven Agenda Blueprint
┌─────────────────────────────────────────────────────────────┐
│ Outcome-Driven Meeting Blueprint │
│ │
│ [ PRIMARY OBJECTIVE ]: The single decision we must make │
│ [ PRE-READ (5 mins) ]: Links & materials to review before │
│ │
│ [ TIME-BLOCKED SEGMENTS ]: │
│ • 00-05m: Alignment & Problem Statement (Lead: Host) │
│ • 05-15m: Core Options & Trade-Offs (Lead: Owner) │
│ • 15-25m: Debate & Edge-Case Q&A (Open Floor) │
│ • 25-30m: Final Decision & Action Item Allocation (Lead: PM)│
└─────────────────────────────────────────────────────────────┘
Master Agenda Prompt Templates
Pattern 1: The 30-Minute Decision Sync Directive
Use when scheduling alignment or approval meetings:
Draft a focused 30-minute meeting agenda for [MEETING PURPOSE: e.g. Q3 Architecture Decision].
Requirements:
1. State the **Single Primary Decision** at the top in bold.
2. Include a **Pre-Meeting Reading / Preparation** section (max 2 items).
3. Create a **Time-Blocked Schedule** breaking down the 30 minutes into 4 tight segments (with designated discussion lead roles).
4. Include a dedicated 5-minute wrap-up block strictly for assigning action items.
Pattern 2: The Cross-Functional Brainstorming Agenda (45 Minutes)
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 Changed · -4 tokens per session bc7579c57451
- 1mo ago First seen · 106 lines · 31 tokens per session scan A 65e4c29db9de
draft-meeting-agendas is a skill published in the GitHub repository alivirgo/Major-AI-Skills (2 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 1,130 once invoked, about $0.0001 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-05.
Other skills, from other repositories
airtable-automation-v2
Airtable Automation via Rube MCP workflow skill. Use this skill when the user needs Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas and the operator should preserve the upstream workflow, copied support files, and provenance before…
airtable-automation-v3
Airtable Automation via Rube MCP workflow skill. Use this skill when the user needs Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas and the operator should preserve the upstream workflow, copied support files, and provenance before…
airtable-automation
Airtable Automation via Rube MCP workflow skill. Use this skill when the user needs Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas and the operator should preserve the upstream workflow, copied support files, and provenance before…
wayfinder
A planning method that maps a large, uncertain project into linked decision tickets in a repository's issue tracker. An issue tracker is a system for recording and organizing project work.
triage
A process for reviewing issues and outside pull requests through category and status labels. An issue is a recorded problem or request, while a pull request is a proposed code change for review.
to-tickets
A method for turning a plan, specification, or conversation into small tickets, where each ticket is a complete vertical slice of work and lists the tickets that must come first.