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 product-on-purpose/pm-skills --skill foundation-meeting-briefgit clone --depth 1 https://github.com/product-on-purpose/pm-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/product-on-purpose/pm-skills/foundation-meeting-brief)<a href="https://agentmods.dev/skills/product-on-purpose/pm-skills/foundation-meeting-brief"><img src="https://agentmods.dev/badge/skills/product-on-purpose/pm-skills/foundation-meeting-brief/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/product-on-purpose/pm-skills/foundation-meeting-brief"><img src="https://agentmods.dev/badge/skills/product-on-purpose/pm-skills/foundation-meeting-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00082 | $0.01774 |
| Opus 5 | $0.00041 | $0.00887 |
| Sonnet 5 | $0.00016 | $0.00355 |
| Haiku 4.5 | $0.00008 | $0.00177 |
Grade A, and why
foundation-meeting-brief 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Brief
A meeting brief is the user's private strategic preparation document for a meeting where context, stakes, or positioning matter. It captures what the user needs to know, what they want to accomplish, who they are engaging with, and how to navigate the conversation. This is strategic prep, not meeting structure, which keeps it distinct from a meeting agenda.
This skill belongs to the Meeting Skills Family. It conforms to the Meeting Skills Family Contract.
When to Use
- Walking into a stakeholder review, exec briefing, or negotiation-adjacent conversation
- First meeting with a new stakeholder where relationship calibration matters
- A meeting where the user needs something from others (capacity commitment, decision, approval)
- Any conversation where specific positioning, messaging, or risk navigation is required
When NOT to Use
- Preparing the agenda attendees will see. Use
foundation-meeting-agendainstead. - Post-meeting summarization. Use
foundation-meeting-recap. - The meeting is low-stakes and well-trodden (recurring team sync, standup). A brief is overhead for these; the agenda alone is sufficient.
Zero-friction execution
Per the family contract, this skill never blocks on interrogation. Default flow:
- Read all provided inputs (topic, attendees, prior recaps, stakeholder summaries, user's primary ask)
- Auto-discover related artifacts via
projectortopicsfrontmatter match - Run inference on missing values (stakeholder positions from prior recaps, primary ask from topic, top-3 goals from meeting type)
- Present a brief inference summary and accept one-word
goor corrections - Produce the brief
If invoked with --go, skip the inference summary. If the user provides all values upfront, no checkpoint appears.
The skill runs on inferred stakeholder positions with low-confidence flags when no stakeholder summaries are provided; it does not block on missing inputs.
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.
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.
- 13d ago First seen · 137 lines · 82 tokens per session scan A df8a47b9b52a
foundation-meeting-brief is a skill published in the GitHub repository product-on-purpose/pm-skills (663 stars, last pushed yesterday), licensed Apache-2.0. It adds 82 tokens to every session and 1,774 once invoked, about $0.0004 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
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.
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.
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.
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.
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.
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.…