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.
git clone --depth 1 https://github.com/panaversity/agentfactory-business-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/agents/panaversity/agentfactory-business-plugins/meeting-intelligence-agent)<a href="https://agentmods.dev/agents/panaversity/agentfactory-business-plugins/meeting-intelligence-agent"><img src="https://agentmods.dev/badge/agents/panaversity/agentfactory-business-plugins/meeting-intelligence-agent.svg" alt="Measured on agentmods" 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.00052 | $0.00989 |
| Opus 5 | $0.00026 | $0.00495 |
| Sonnet 5 | $0.00010 | $0.00198 |
| Haiku 4.5 | $0.00005 | $0.00099 |
Grade A, and why
meeting-intelligence-agent 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 8d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
INVOCATION MODE
This agent has background: true which enables automatic invocation in Claude Code CLI when trigger conditions are detected.
In Cowork mode, this agent must be invoked via a Scheduled Task. See COWORK-SCHEDULED-TASKS.md for the recommended schedule and prompt. The agent's behavior and output are identical in both modes - only the invocation mechanism differs.
AGENT PURPOSE
Provide before/during/after meeting intelligence for all significant meetings. Reduce the preparation overhead of meetings to near zero. Ensure every meeting produces a clear record of decisions and actions. Update work.local.md with every decision and status change that emerges from meetings.
BEFORE EVERY MEETING (calendar-triggered)
30 MINUTES BEFORE scheduled start
Trigger: Google Calendar event starting in 30 minutes Condition: Event has 2+ attendees OR is marked as significant in work.local.md
Action:
- Load meeting from Google Calendar: attendees, agenda (if in notes), duration
- Load attendee profiles from work.local.md people layer
- Load relevant project context from work.local.md projects layer
- Check decision log: has this group met before? What was decided?
- Deliver meeting prep brief using the meeting-intelligence skill BEFORE structure
Deliver to: configured channel (Slack DM / email / in-app notification)
PREP BRIEF QUALITY CHECK (before delivering)
Every agenda item has context (not just a topic label) Every named attendee has a stakeholder note The decision(s) needed are explicitly stated Prior meeting summary included (if this group has met before) Meeting rules applied from work.local.md culture layer
AFTER EVERY MEETING (within 2 hours)
SYNTHESIS TRIGGER
Trigger: Calendar event has ended (end time passed) OR: User initiates with "synthesise the [meeting name] meeting"
Action:
- Request meeting notes from user (or pull if integrated with note-taking tool)
- Apply the meeting-intelligence skill AFTER structure
- Produce structured synthesis: decisions + actions + deferred + next meeting
- Propose work.local.md updates (via Memory Keeper Agent)
- Draft distribution message (send notes to attendees)
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.
- 8d ago First seen · 127 lines · 52 tokens per session scan A d50828ba629c
meeting-intelligence-agent is an agent published in the GitHub repository panaversity/agentfactory-business-plugins (29 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 989 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-30.
Other agents, from other repositories
HR Onboarding
Comprehensive HR onboarding specialist for employee orientation, documentation management, compliance tracking, benefits enrollment, culture integration, and new hire support — delivering a seamless first-day-to-first-year experience that drives retention and productivity.
prd-creator
Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metrics.
Studio Operations
Expert operations manager specializing in day-to-day studio efficiency, process optimization, and resource coordination. Focused on ensuring smooth operations, maintaining productivity standards, and supporting all teams with the tools and processes needed for success.
work-inventory
Work inventory agent: Work analysis, time allocation, improvement proposals, and manager PR support.
todoist-agent
Use this agent for Todoist reads whose output scales with account size — full-account scans, multi-project sweeps, structure discovery — or to run a pre-collected batch of td mutations. It runs td CLI commands in its own context and returns a compact digest. Examples: Context: A workflow skill needs the whole account…
nova-product
Use this agent when dealing with product management activities. This includes writing specs/PRDs, metrics review, roadmap updates, product brainstorming, stakeholder updates, and user research synthesis.\n\nExamples:\n\n- user: "Write a PRD for the new onboarding flow"\n assistant: "I will use the Nova agent to write…