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 britt/agent-skills --skill prepare-meeting-agendagit clone --depth 1 https://github.com/britt/agent-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/britt/agent-skills/prepare-meeting-agenda)<a href="https://agentmods.dev/skills/britt/agent-skills/prepare-meeting-agenda"><img src="https://agentmods.dev/badge/skills/britt/agent-skills/prepare-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.
<a href="https://agentmods.dev/skills/britt/agent-skills/prepare-meeting-agenda"><img src="https://agentmods.dev/badge/skills/britt/agent-skills/prepare-meeting-agenda.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.00055 | $0.00704 |
| Opus 5 | $0.00028 | $0.00352 |
| Sonnet 5 | $0.00011 | $0.00141 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
prepare-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.
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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare Meeting Agenda Skill
Generate structured meeting agendas by gathering context from recent project activity.
When to Use
Activate when preparing for:
- Sprint planning sessions
- Retrospectives
- Standups or syncs
- Project check-ins
- Any recurring team meeting
When NOT to use: not for taking minutes during or after a meeting, or one-off external meetings with no project activity to mine.
Workflow
- Identify meeting type - Determine format and focus areas
- Gather context - Requires the
ghCLI authenticated to the repo. Rungh issue list --state open --json number,title,labels,updatedAtandgh pr list --state all --json number,title,updatedAt, filtered to the meeting period (e.g. items updated since the last meeting), plus any project notes. If no repo is available, ask the user for topics. - Group by topic - Organize items logically
- Assign owners - Assign owners from issue/PR assignees when available; otherwise leave [Name] placeholders for the organizer
- Estimate time - Allocate realistic durations
- Output agenda - Format using template below
Meeting Types
Sprint Planning
- Focus: upcoming work, priorities, capacity
- Sources: backlog issues, milestone items
- Include: estimates, assignments, dependencies
Retrospective
- Focus: what worked, what didn't, improvements
- Sources: completed issues, incident notes, team feedback
- Include: wins to celebrate, problems to address
Standup/Sync
- Focus: progress, blockers, today's priorities
- Sources: in-progress issues, recent commits
- Include: quick updates, blockers needing help
Project Check-in
- Focus: overall status, risks, upcoming milestones
- Sources: milestone progress, recently merged PRs, open blockers
- Include: status summary, decisions needed, next steps
Agenda Template
## [Meeting Type] - [Date]
**Attendees**: [list or "team"]
**Duration**: [X minutes]
### Topics
| Topic | Owner | Time |
|-------|-------|------|
| [Item] | [Name] | [5m] |
### Discussion Items
- **[Topic 1]**: [brief context]
- **[Topic 2]**: [brief context]
### Carryover from Last Meeting
- [ ] [Incomplete action item]
### Notes
[Space for meeting notes]
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.
- 12d ago First seen · 90 lines · 55 tokens per session scan A 9be6387b134a
prepare-meeting-agenda is a skill published in the GitHub repository britt/agent-skills (5 stars, last pushed 9d ago), licensed MIT. It adds 55 tokens to every session and 704 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.
remove
Remove a deployed framework or addon from the current workspace.