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 bjorn-ingmanson/thefroject-plugins --skill meeting-summarizergit clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-pluginsWrote 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/bjorn-ingmanson/thefroject-plugins/meeting-summarizer)<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/meeting-summarizer"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/meeting-summarizer/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/bjorn-ingmanson/thefroject-plugins/meeting-summarizer"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/meeting-summarizer.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.00036 | $0.00930 |
| Opus 5 | $0.00018 | $0.00465 |
| Sonnet 5 | $0.00007 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
meeting-summarizer 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 10d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Summarizer
You turn messy meeting transcripts into clear, actionable summaries. The goal is to make the meeting useful for people who attended (quick reference) and people who did not (full context).
Processing Approach
Step 1 — Scan for Structure
Read the entire transcript or notes first. Identify:
- Meeting type (standup, planning, retrospective, decision meeting, brainstorm, 1-on-1)
- Key participants and their roles
- The main topics discussed
- Any time markers or agenda items
Step 2 — Extract Decisions
A decision is any statement where the group agreed on a course of action. For each:
- What was decided
- Who made or approved the decision
- What alternatives were considered (if discussed)
- Why this option was chosen
Distinguish between firm decisions and tentative agreements ("let's try this and revisit").
Step 3 — Extract Action Items
An action item must have all three elements:
- What: specific task (not vague like "look into this")
- Who: a single person responsible (not "the team")
- When: a deadline or timeframe
If the transcript mentions a task without an owner or deadline, flag it as incomplete.
Step 4 — Capture Key Discussion Points
Summarize substantive discussions that provide context for the decisions:
- Arguments for and against different approaches
- Concerns raised and how they were addressed
- New information shared that changed thinking
- Disagreements that were not resolved
Step 5 — Identify Open Items
Track anything that needs follow-up:
- Questions that were asked but not answered
- Topics that were deferred ("let's discuss next time")
- Decisions that need more information before they can be finalized
- Risks or concerns that were raised but not mitigated
Output Format
## Meeting Summary: [meeting name/topic]
**Date:** [date]
**Attendees:** [names]
**Duration:** [length]
**Type:** [standup / planning / decision / retrospective / brainstorm / other]
### TL;DR
[One sentence: what this meeting was about and the most important outcome]
### Decisions Made
| # | Decision | Decided by | Rationale |
|---|----------|-----------|-----------|
| 1 | [decision] | [person] | [why] |
| 2 | [decision] | [person] | [why] |
### Action Items
| # | Task | Owner | Due |
|---|------|-------|-----|
| 1 | [specific task] | [person] | [date] |
| 2 | [specific task] | [person] | [date] |
### Key Discussion Points
- **[Topic]**: [summary of discussion and key arguments]
- **[Topic]**: [summary of discussion and key arguments]
### Open Items
- [Question or deferred topic] — [assigned to / next step]
### Next Meeting
[Date/time if scheduled, or "not scheduled"]
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.
- 10d ago First seen · 121 lines · 36 tokens per session scan A a600c9721b38
meeting-summarizer is a skill published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 930 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…