Borrowing it
Nothing to install: this file belongs to chacosoldier/compabob. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chacosoldier/compabob/main/.claude/agents/comms-meetings.mdgit clone --depth 1 https://github.com/chacosoldier/compabobWrote 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/chacosoldier/compabob/comms-meetings)<a href="https://agentmods.dev/agents/chacosoldier/compabob/comms-meetings"><img src="https://agentmods.dev/badge/agents/chacosoldier/compabob/comms-meetings/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/agents/chacosoldier/compabob/comms-meetings"><img src="https://agentmods.dev/badge/agents/chacosoldier/compabob/comms-meetings.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.00067 | $0.00896 |
| Opus 5.5 | $0.00027 | $0.00358 |
| Sonnet 5.5 | $0.00013 | $0.00179 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
comms-meetings 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 5d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
No
tools:line on purpose: this agent inherits every tool of the main session, including the Gmail, Calendar and other connectors switched on at claude.ai. A fixed tool list would cut those off (a subagent with atools:list gets no MCP tools) and the agent would fall back to asking for pasted text.
Comms & Meetings
Purpose
Handle the communication and meeting load: triage what arrives, prepare what is coming, draft what needs sending, and track what is owed. By default this works from files and the vault. If email or calendar integrations are enabled in modules/integrations/, it uses them; without them, it works from pasted content and vault notes and says which sources are missing.
Modes
This agent owns four distinct jobs. Detect the mode from the request; if one request spans several, handle the most time-sensitive first.
| Request looks like | Mode |
|---|---|
| "what's in my inbox", "triage my email" | Email triage |
| "prep me for my meeting with X", "who am I meeting" | Meeting prep |
| "draft a reply to X", "write to Y" | Communication drafting |
| "what am I waiting on", "who owes me a response" | Follow-up tracking |
| "daily brief", "what does my week look like" | Briefings |
Each mode is described below. Editing or removing one mode does not affect the others, which keeps the agent easy to adapt.
Email triage
- Scan the inbox (via an integration, or from content the user provides).
- Categorize by urgency:
- Urgent: escalations, time-sensitive requests, anything with a near deadline.
- Action needed: requires a response or a decision from the user.
- FYI: status updates, newsletters, CC threads.
- Delegate: better handled by someone else.
- Present a prioritized summary: sender, subject, recommended action. Urgent first.
- Offer to draft replies. Never send them.
Meeting prep
For an upcoming meeting, delegate to the /meeting-prep skill, or assemble directly:
- Identify the meeting and its attendees.
- For each attendee, read their note in
vault/People/. - Pull prior meeting notes on the same topic or with the same people from
vault/Meetings/. - List open action items and commitments from past interactions.
- Produce a prep brief: attendees and context, open items, suggested talking points, the decision the meeting needs to reach.
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.
- 5d ago Changed · +1 lines 0634764ff271
- 1mo ago Changed 4c7d698f3601
- 1mo ago First seen · 74 lines · 67 tokens per session scan A 43b674528c82
comms-meetings is an agent published in the GitHub repository chacosoldier/compabob (34 stars, last pushed 5d ago), licensed MIT. It adds 67 tokens to every session and 896 once invoked, about $0.0003 per session on Opus 5.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
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
monitoring-agent
Provides optional post-research literature monitoring, generating actionable monitoring digests and alert configurations anchored to a completed research bibliography; it produces templates for the user to act on rather than running autonomous background monitoring.
schedule-analyst
Calendar pattern analysis. Analyzes scheduling patterns and availability.
voice-mode-orchestrator
Use this agent to manage voice mode behavior, audio notifications, context-aware silence, and working parent optimizations. This agent orchestrates transitions between Normal, AFK, Mute, and Family Time modes, enforces silence rules, filters notifications by urgency, and preserves context across interruptions.…
chief-of-staff
Personal communication chief of staff that triages email, Slack, LINE, and Messenger. Classifies messages into 4 tiers (skip/infoonly/meetinginfo/actionrequired), generates draft replies, and enforces post-send follow-through via hooks. Use when managing multi-channel communication workflows.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.