foundation-meeting-agenda

foundation-meeting-agenda is a skill for Claude Code from product-on-purpose/pm-skills. It costs 101 tokens per session (2,312 once invoked), scanned A, original, Apache-2.0.

An attendee-facing plan for a meeting that states the topics, owners, timing, and expected outcomes. It is meant to be shared with participants before the meeting.

In plain words
What is it for?
Use it for standups, planning sessions, reviews, decision meetings, brainstorms, one-to-ones, kickoffs, and other structured meetings.
Why use it?
It prevents meetings from drifting by making the purpose, responsibilities, and definition of success clear in advance.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the pm-skills plugin — 69 skills, 11 commands, 6 agents, 2 hooks shipped together

Good fit Use it for standups, planning sessions, reviews, decision meetings, brainstorms, one-to-ones, kickoffs, and other structured meetings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/product-on-purpose/pm-skills/foundation-meeting-agenda
Install

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.

Any agent
npx skills add product-on-purpose/pm-skills --skill foundation-meeting-agenda
Clone the repo
git clone --depth 1 https://github.com/product-on-purpose/pm-skills

Made for: Claude Code.

Or install pm-skills, the plugin that ships this one along with the rest of its 69 skills, 11 commands, 6 agents, 2 hooks.

Wrote 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.

agentmods badge for foundation-meeting-agenda

README.md
[![agentmods](https://agentmods.dev/badge/skills/product-on-purpose/pm-skills/foundation-meeting-agenda/github.svg)](https://agentmods.dev/skills/product-on-purpose/pm-skills/foundation-meeting-agenda)
Your own site
<a href="https://agentmods.dev/skills/product-on-purpose/pm-skills/foundation-meeting-agenda"><img src="https://agentmods.dev/badge/skills/product-on-purpose/pm-skills/foundation-meeting-agenda/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.

agentmods 80×15 button for foundation-meeting-agenda

Your own site · 80×15
<a href="https://agentmods.dev/skills/product-on-purpose/pm-skills/foundation-meeting-agenda"><img src="https://agentmods.dev/badge/skills/product-on-purpose/pm-skills/foundation-meeting-agenda.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 101 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,312 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 27 Apr 2026
  • Snyk pass 27 Apr 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00101 $0.02312
Opus 5 $0.00051 $0.01156
Sonnet 5 $0.00020 $0.00462
Haiku 4.5 $0.00010 $0.00231

Measured 13d ago against content hash 03f82bd0c281, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

foundation-meeting-agenda 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 13d 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.

skills/foundation-meeting-agenda/SKILL.md · 163 lines

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.

Meeting Agenda

A meeting agenda is the attendee-facing structural document that sets expectations before a meeting. It answers "what will we discuss, who owns each topic, how will we spend the time, and what does done look like?" Distinct from a meeting brief, which is the user's private strategic prep; the agenda is shared with participants and focused on structure and flow.

This skill belongs to the Meeting Skills Family. It conforms to the Meeting Skills Family Contract, which defines shared frontmatter, file naming, the go-mode behavioral pattern, and universal output requirements across all meeting skills.

When to Use

  • Running or chairing a cross-functional working session, project kickoff, stakeholder review, or decision meeting
  • Any meeting with more than three attendees or more than thirty minutes
  • Recurring meeting where a rolling structure (1-on-1, team sync) needs fresh framing each time
  • Mid-initiative alignment moment where explicit desired outcomes prevent drift

When NOT to Use

  • The user's preparation is private and tactical (positioning, stakeholder reads, asks). Use foundation-meeting-brief instead.
  • The meeting has already happened. Use foundation-meeting-recap for post-meeting summarization.
  • The user wants to communicate outcomes to non-attendees. Use foundation-stakeholder-update after the meeting.

Zero-friction execution

Per the family contract, this skill never blocks on interrogation. Default flow:

  1. Read all provided inputs (topic, any referenced files, attendee list, constraints)
  2. Run inference on missing values (meeting type from topic keywords, duration default, objective from topic phrasing, attendee roles from context)
  3. Present a brief inference summary and accept one-word go or corrections
  4. Produce the agenda

If invoked with --go, skip the inference summary and produce output directly using defaults (duration 30 min, meeting type other, and so on). If the user provides all values upfront, no checkpoint appears.

Read the full file on GitHub · 163 lines

Files

What ships with it

4 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.

Changes

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.

  1. 13d ago First seen · 163 lines · 101 tokens per session scan A 03f82bd0c281

Subscribe to this mod's changes

foundation-meeting-agenda is a skill published in the GitHub repository product-on-purpose/pm-skills (663 stars, last pushed yesterday), licensed Apache-2.0. It adds 101 tokens to every session and 2,312 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

idea-validator

Use when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something. Do NOT use for prioritizing an existing backlog or reviewing a shipped feature — those need RICE scoring or a design review instead.

aakashg/pm-claude-skills · 59 tokens

product-designer

Use when the user asks to review a design, critique a UI or mockup, give design feedback, or check a screen for usability and accessibility issues. Do NOT use for visual brand or aesthetic preference debates, or for reviewing copy before layout is settled.

aakashg/pm-claude-skills · 55 tokens

prompt-engineer

Use when the user asks to improve, optimize, rewrite, debug, or shorten a prompt, or asks why a prompt is producing bad output. Do NOT use for writing a Claude Code SKILL.md — that needs skill structure rules, not prompt techniques.

aakashg/pm-claude-skills · 55 tokens

status-update-writer

Use when the user asks to write a status update, weekly or monthly update, stakeholder update, project update, standup, status report, or QBR. Do NOT use for writing a PRD or a retro doc — those need different structures.

aakashg/pm-claude-skills · 55 tokens

linkedin-post-writer

Use when the user asks to write, draft, or rewrite a LinkedIn post, turn notes or an article into a LinkedIn post, or fix a hook that is not landing. Do NOT use for X/Twitter threads, newsletters, or blog posts — those need different length and hook rules.

aakashg/pm-claude-skills · 65 tokens

spec-from-conversation

Turn an unstructured stakeholder conversation, Slack thread, or meeting transcript into a structured spec (problem, goals, non-goals, success metrics, open questions). Use whenever a PM has raw conversational input and needs a first-draft spec, or when someone says "can you turn this into a doc" after a discussion.…

ianklassen/pm-skills · 108 tokens