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 agentmods add agents/chacosoldier/compabob/comms-meetingsgit 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.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 | $0.00067 | $0.00846 |
| Opus 5 | $0.00034 | $0.00423 |
| Sonnet 5 | $0.00013 | $0.00169 |
| Haiku 4.5 | $0.00007 | $0.00085 |
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 4d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
- 4d ago First seen · 74 lines · 67 tokens per session scan A 43b674528c82
comms-meetings is an agent published in the GitHub repository chacosoldier/compabob (32 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 846 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
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
ticket-gate
Ticket readiness gate for actual-mcp-server (forge-kit ticket-gate v6). Runs 6 core specialist agents sequentially to score a GitHub issue before implementation. Each agent scores 1-10; ALL must score 10 to pass. An agent whose domain the ticket does not touch auto-scores 10 (N/A). Extra specialists are added by…
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
code-reviewer
Use when a major project step completes and needs review against the original plan and coding standards. Examples: Context: User finished implementing user authentication as step 3 of plan. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Let me use the…
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.