teams-meeting-pipeline

teams-meeting-pipeline is a skill for Claude Code, Codex from StarryCod/cogitum. It costs 32 tokens per session (1,566 once invoked), scanned A, a copy of teams-meeting-pipeline, MIT.

A command-line pipeline for processing Microsoft Teams meetings, including summaries, transcripts, recordings, and action items. Microsoft Teams is a tool for online meetings and workplace chat.

In plain words
What is it for?
Use it to summarize meetings, inspect or replay processing jobs, check setup, and manage Microsoft Graph subscriptions that deliver meeting events.
Why use it?
It helps turn meeting data into notes and tasks, and provides checks for jobs that fail or stop receiving new meetings.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to summarize meetings, inspect or replay processing jobs, check setup, and manage Microsoft Graph subscriptions that deliver meeting events.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/starrycod/cogitum/teams-meeting-pipeline
Install

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.

Any agent
npx skills add StarryCod/cogitum --skill teams-meeting-pipeline
Clone the repo
git clone --depth 1 https://github.com/StarryCod/cogitum

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for teams-meeting-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/skills/starrycod/cogitum/teams-meeting-pipeline/github.svg)](https://agentmods.dev/skills/starrycod/cogitum/teams-meeting-pipeline)
Your own site
<a href="https://agentmods.dev/skills/starrycod/cogitum/teams-meeting-pipeline"><img src="https://agentmods.dev/badge/skills/starrycod/cogitum/teams-meeting-pipeline/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.

agentmods 80×15 button for teams-meeting-pipeline

Your own site · 80×15
<a href="https://agentmods.dev/skills/starrycod/cogitum/teams-meeting-pipeline"><img src="https://agentmods.dev/badge/skills/starrycod/cogitum/teams-meeting-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,566 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 94% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.01566
Opus 5 $0.00016 $0.00783
Sonnet 5 $0.00006 $0.00313
Haiku 4.5 $0.00003 $0.00157

Measured 7d ago against content hash dfa9bc37966a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

teams-meeting-pipeline 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 7d 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.

Origin

This is a copy

94% identical to teams-meeting-pipeline — 52 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

cogitum/data/skills/productivity/teams-meeting-pipeline/SKILL.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Teams Meeting Pipeline

Use this skill whenever the user asks about Microsoft Teams meeting summaries, transcripts, recordings, action items, Graph subscriptions, or any operational question about the Teams meeting pipeline. Works in any language — the triggers below are examples, not an exhaustive list.

Everything operator-facing is a cog teams-pipeline subcommand run via the terminal tool. There are no new model tools for this pipeline — the CLI is the surface.

When to use this skill

The user is asking to:

  • summarize a Teams meeting / extract action items / pull meeting notes
  • check pipeline status, inspect a stored meeting job, or see recent meetings
  • replay / re-run a stored job that failed or needs a fresh summary
  • validate Microsoft Graph setup after changing env or config
  • troubleshoot "meeting summary never arrived" or "no new meetings are ingesting"
  • manage Graph webhook subscriptions (create, renew, delete, inspect)
  • set up automated subscription renewal (see pitfall below)

Multilingual trigger examples (not exhaustive):

  • English: "summarize the Teams meeting", "pipeline status", "replay job X"
  • Turkish: "Teams meeting özetle", "action item çıkar", "toplantı notu", "pipeline durumu", "replay job"

Prerequisites

Before using the pipeline, verify these are set in ~/.config/cogitum/.env:

MSGRAPH_TENANT_ID=...
MSGRAPH_CLIENT_ID=...
MSGRAPH_CLIENT_SECRET=...

If any are missing, direct the user to the Azure app registration guide at /docs/guides/microsoft-graph-app-registration — they need an Azure AD app registration with admin-consented Graph application permissions before the pipeline will work.

Command reference

Status and inspection (start here)

cog teams-pipeline validate              # config snapshot — run first after any change
cog teams-pipeline token-health          # Graph token status
cog teams-pipeline token-health --force-refresh   # force a fresh token acquisition
cog teams-pipeline list                  # recent meeting jobs
cog teams-pipeline list --status failed  # only failed jobs
cog teams-pipeline show <job-id>         # full detail of one job
cog teams-pipeline subscriptions         # current Graph webhook subscriptions

Read the full file on GitHub · 117 lines

Changes

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.

  1. 7d ago First seen · 117 lines · 32 tokens per session scan A dfa9bc37966a

Subscribe to this mod's changes

teams-meeting-pipeline is a skill published in the GitHub repository StarryCod/cogitum (11 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 1,566 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to teams-meeting-pipeline, differing in 52 lines, and is treated as a copy.

Related

Other skills, from other repositories