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 AlekseiUL/agentforge-openclaw --skill meeting-prepgit clone --depth 1 https://github.com/AlekseiUL/agentforge-openclawWrote 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/alekseiul/agentforge-openclaw/meeting-prep)<a href="https://agentmods.dev/skills/alekseiul/agentforge-openclaw/meeting-prep"><img src="https://agentmods.dev/badge/skills/alekseiul/agentforge-openclaw/meeting-prep.svg" alt="Measured on agentmods" 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.00055 | $0.00716 |
| Opus 5 | $0.00028 | $0.00358 |
| Sonnet 5 | $0.00011 | $0.00143 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
meeting-prep 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- meeting-prep — 100% identical, 0 lines differ
What it actually says
Meeting Prep
Помогает подготовиться к встречам: agenda, ключевые вопросы, шаблон заметок, follow-up. Тип: Workflow с Progressive Disclosure.
Алгоритм
Шаг 1. Контекст встречи
Спроси (по одному):
- С кем встреча? (клиент / коллега / инвестор / партнёр)
- Тема/цель?
- Сколько времени? (15 мин / 30 мин / 60 мин)
- Первая встреча или повторная?
Шаг 2. Agenda
Сгенерируй agenda по формату:
## Agenda: [тема]
Дата: [дата] | Время: [длительность]
Участники: [список]
1. [Тема блока] (X мин)
- Ключевой вопрос
2. [Тема блока] (X мин)
- Ключевой вопрос
3. Next steps (5 мин)
Правила:
- Последние 5 минут ВСЕГДА на next steps
- Не больше 4-5 блоков на 30-минутную встречу
- Каждый блок = один ключевой вопрос
Шаг 3. Подготовительные вопросы
Предложи 3-5 вопросов которые стоит задать. Два типа:
- Открытые (для понимания): "Как вы видите..."
- Конкретные (для решений): "Какой дедлайн по..."
Шаг 4. Шаблон заметок
## Заметки: [тема] - [дата]
### Присутствовали
-
### Ключевые решения
1.
2.
### Действия (кто / что / когда)
1. [ ]
2. [ ]
### Открытые вопросы
-
Шаг 5. Follow-up (после встречи)
Если пользователь говорит "встреча прошла" или делится заметками:
- Сформируй follow-up сообщение (email/сообщение)
- Выдели action items с ответственными и дедлайнами
- Предложи дату следующей встречи если нужно
Детали по типам встреч (клиент, инвестор, 1-on-1) - см. references/ когда появятся.
Примеры
Запрос: "Готовлюсь к звонку с клиентом, 30 минут, обсуждаем новый проект"
Ответ:
## Agenda: Обсуждение нового проекта
Время: 30 мин
1. Контекст и цели проекта (10 мин)
- Какую проблему решаем?
2. Объём работ и ожидания (10 мин)
- Что входит в MVP?
3. Сроки и бюджет (5 мин)
- Когда нужен результат?
4. Next steps (5 мин)
Вопросы к клиенту:
- Кто принимает финальное решение?
- Есть ли жёсткий дедлайн?
- Какой бюджет рассматриваете?
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.
- 8d ago First seen · 98 lines · 55 tokens per session scan A e36016efa93e
meeting-prep is a skill published in the GitHub repository AlekseiUL/agentforge-openclaw (43 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 716 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-08-30.
Other skills, from other repositories
laohan-gengxin
A tool-version checking and update workflow. It compares installed versions of tools from sources such as npm, Homebrew, pip, uv, GitHub, plugins, and skills with their latest available versions.
lark-vc-agent
A meeting assistant for Feishu video calls that can join or leave an ongoing meeting, read visible live events, and send text or reactions. Feishu is a workplace collaboration platform.
wechat-business-news-cron
Set up recurring morning/evening news digests delivered to WeChat or Feishu via Hermes cron jobs, with manual timezone conversion, duplicate-job cleanup, and a polished Chinese business-brief card format.
notion
Notion API for creating and managing pages, databases, and blocks.
gog
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
caldav-calendar
Sync and query CalDAV calendars (iCloud, Google, Fastmail, Nextcloud, etc.) using vdirsyncer + khal. Works on Linux.