meeting-agenda

meeting-agenda is a skill for Claude Code from tkcostello/pastor-ai-skills. It costs 47 tokens per session (2,378 once invoked), scanned A, original, MIT.

A meeting-agenda planning workflow for church meetings such as staff meetings, boards, committees, volunteer huddles, and one-on-ones.

In plain words
What is it for?
It helps prioritise discussion and decision items, assign time, identify required reports or decisions, and structure the opening and closing.
Why use it?
It turns a list of topics and a time limit into a realistic agenda and flags items that will not fit.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths.

Part of the pastor-skills plugin — 15 skills shipped together

Good fit It helps prioritise discussion and decision items, assign time, identify required reports or decisions, and structure the opening and closing.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tkcostello/pastor-ai-skills/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 tkcostello/pastor-ai-skills --skill meeting-agenda
Clone the repo
git clone --depth 1 https://github.com/tkcostello/pastor-ai-skills

Made for: Claude Code.

Or install pastor-skills, the plugin that ships this one along with the rest of its 15 skills.

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 meeting-agenda

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/tkcostello/pastor-ai-skills/meeting-agenda"><img src="https://agentmods.dev/badge/skills/tkcostello/pastor-ai-skills/meeting-agenda.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,378 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
  • 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.00047 $0.02378
Opus 5 $0.00023 $0.01189
Sonnet 5 $0.00009 $0.00476
Haiku 4.5 $0.00005 $0.00238

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

Security

Grade A, and why

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 12d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (generate-pdf.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/meeting-agenda/SKILL.md · 242 lines

How it starts

The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Meeting Agenda Builder

Run meetings that end on time and actually decide things.

Before writing: follow the pastor-foundation skill and load the church profile from ~/.claude/pastor-profile.md. If the profile file is missing, run the pastor-setup skill first.


What You Need to Provide

To build your agenda, give me the following:

  • Meeting type: Staff meeting, elder/deacon board, volunteer huddle, committee, or one-on-one
  • Topics or items to cover: List everything you want to address
  • Time available: Total meeting length (example: "60 minutes")
  • Optional: Decisions that must be made, reports expected, people attending

The more context you give, the tighter the agenda. If you're not sure what you need, list your topics and I'll help you shape it.


Step 1: Assess and Prioritize

Before building the agenda, I evaluate whether your items fit your time.

Rule of thumb:

  • Discussion or decision item: 10-15 minutes each
  • Update or report: 5 minutes each
  • Opening and closing: 7 minutes combined (non-negotiable)

If your list doesn't fit, I'll flag it and recommend what to cut, defer, or consolidate. The goal is a realistic agenda, not an aspirational one nobody follows.

Common problems I'll flag:

  • More than 4-5 substantive items in a 60-minute meeting
  • Decision items buried at the end where time always runs out
  • Reports that could be sent via email instead of discussed live
  • Items that belong in a different meeting type entirely

Step 2: Build the Agenda

Every agenda follows this format:


## [Meeting Type] Agenda
**Date:** [date]
**Time:** [start] - [end] ([total] minutes)
**Location:** [if provided]

---

### Opening (5 min)
- Opening prayer / brief devotional with scripture suggestion
- Quick check-in: "What's one win from this week?"

### [Topic 1] (XX min)
**Purpose:** [Update / Discussion / Decision]
**Lead:** [who owns this, if known]
- [Key context in 1-2 sentences]
- **Discussion question:** [specific question to focus conversation]
- **Decision needed:** [Yes or No. If yes, state exactly what needs to be decided.]

### [Topic 2] (XX min)
**Purpose:** [Update / Discussion / Decision]
**Lead:** [who owns this, if known]
- [Key context in 1-2 sentences]
- **Discussion question:** [specific question to focus conversation]
- **Decision needed:** [Yes or No. If yes, state exactly what needs to be decided.]

### Action Items and Next Steps (5 min)
- Review decisions made in this meeting
- Assign action items with owners and deadlines
- Confirm next meeting date

### Closing (2 min)
- Closing prayer or brief word of encouragement

---

**Time check:** [Total allocated vs. available]
**Parking lot:** [Items deferred to a future meeting]

Read the full file on GitHub · 242 lines

Files

What ships with it

1 file 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. 12d ago First seen · 242 lines · 0 tokens per session scan A 31aad22384fb

Subscribe to this mod's changes

meeting-agenda is a skill published in the GitHub repository tkcostello/pastor-ai-skills (52 stars, last pushed 15d ago), licensed MIT. It adds 47 tokens to every session and 2,378 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-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens