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 tatargabor/set-copilot --skill meeting-copilotgit clone --depth 1 https://github.com/tatargabor/set-copilotWrote 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/tatargabor/set-copilot/meeting-copilot)<a href="https://agentmods.dev/skills/tatargabor/set-copilot/meeting-copilot"><img src="https://agentmods.dev/badge/skills/tatargabor/set-copilot/meeting-copilot.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.00022 | $0.07970 |
| Opus 5 | $0.00011 | $0.03985 |
| Sonnet 5 | $0.00004 | $0.01594 |
| Haiku 4.5 | $0.00002 | $0.00797 |
Grade A, and why
meeting-copilot 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 3d 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 — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Copilot Skill
Real-time meeting assistant that monitors a live transcript and cross-references what's being said against the project's knowledge base, specs, and past decisions. Powered by set-copilot.
The copilot is NOT a separate AI — it IS this Claude Code session. The set-copilot capture process handles audio + transcription; Claude Code handles analysis via a Monitor loop + filesystem access to your knowledge base. The only external dependency is Soniox for transcription.
Both halves are config, not code:
- Knowledge —
knowledge.sources(dirs, files, or globs),knowledge.decisions,knowledge.keywords. The digest step reads those and produces three artifacts the copilot consumes. - Policy —
copilot.alerts(what to speak up about) andcopilot.instructions(a project-owned markdown file of domain rules), rendered bynpx set-copilot prompt.
Usage
/meeting-copilot start (or start --lite / start --zero)
IMPORTANT: Execute ALL phases sequentially without stopping. Do NOT wait for user input between phases. Do NOT use forks or subagents — do everything inline.
Three modes:
start(default) — active lookup: pre-loads the digest, then uses Grep/Read onknowledge.sourcesduring the meeting. Slower (~3-8s) but precise.start --lite— pre-loaded context: loads the enriched JSON at Phase 1, then zero tool calls during the meeting. Fast (<1s) but limited to pre-loaded knowledge.start --zero— zero-load: skips Phase 1 entirely. Works purely from what's already in the conversation context (CLAUDE.md, rules, memory). Fastest start, smallest footprint.
Wall option (start wall). Add the word wall (combinable with any mode, e.g. start --lite wall) to have the copilot own the monitor wall: it launches the wall itself in Phase 2b — scoped to the SAME runtime dir as the capture, on a per-session port, fake-feed off — and tears it down in stop. This is the supported way to run the wall; do NOT hand-start set-copilot wall in another terminal against a different dir (that split is what makes drawings and transcript point at different places). Without wall, no wall is started and Phase 5 simply skips emitting.
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.
- 3d ago First seen · 448 lines · 22 tokens per session scan A 39ab1fda83a4
meeting-copilot is a skill published in the GitHub repository tatargabor/set-copilot (2 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 7,970 once invoked, about $0.0001 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-09-04.
Other skills, from other repositories
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
Migrate
Intakes external content, classifies chunks against LifeOS taxonomy, commits with provenance. Sources: .md/.txt, stdin, LifeOS dirs, CLAUDE.md/Cursor/OpenAI Custom Instructions, Obsidian/Notion/Apple Notes exports. MigrateScan classifies → routing table. MigrateApprove with…
daily-briefing
Proactive daily briefing that fires on a recurring schedule, pulls recent memory and workspace context, composes a structured summary (action items, progress, radar, next steps), and delivers it to all active channels. Enable with a time like "set up my daily briefing at 9am". Disable, reschedule, or check status at…
company-brain
Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so Claude can answer questions on your team's behalf. Team-scope sibling to second-brain (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki…
calendar
Manage calendar events via CalDAV (Google/iCloud/Nextcloud) or local ICS files. View, create, and query events.
email-assistant
Read, search, draft, and send emails via Himalaya CLI or Python IMAP/SMTP. Requires email account configuration.