Borrowing it
Nothing to install: this file belongs to gtapps/msteams-channel. 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/gtapps/msteams-channel/main/CLAUDE.mdgit clone --depth 1 https://github.com/gtapps/msteams-channelWrote 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/instructions/gtapps/msteams-channel/claude-md)<a href="https://agentmods.dev/instructions/gtapps/msteams-channel/claude-md"><img src="https://agentmods.dev/badge/instructions/gtapps/msteams-channel/claude-md.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.02489 | $0.02489 |
| Opus 5 | $0.01244 | $0.01244 |
| Sonnet 5 | $0.00498 | $0.00498 |
| Haiku 4.5 | $0.00249 | $0.00249 |
Grade A, and why
msteams-channel CLAUDE.md 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Commands
Runtime is Bun (no Node, no bundler, no build step — TypeScript runs directly).
bun test # whole suite (394 tests, ~14s, no tenant/network)
bun test tests/gate.test.ts # one file
bun test -t "outbound" # one test by name
bun run typecheck # tsc --noEmit; must pass before committing
bun server.ts # run the MCP server standalone (stderr is the only log)
bun send.ts --list # proactive-send CLI: list reachable conversations
Running the plugin for real needs two things beyond installing it — a managed-settings
allowlist entry and claude --channels plugin:msteams@msteams-channel. See
README.md "Two-step enablement"; without both, inbound events are dropped silently.
Architecture
One Bun process (server.ts) is simultaneously:
- an MCP stdio server Claude Code spawns (tools +
claude/channelcapability), and - the Teams webhook listener (
@microsoft/teams.appsApp, served by our ownsrc/bun-adapter.tsinstead of the SDK's express adapter).
Same shape as the official telegram plugin, where the poller lives inside the MCP process.
server.ts starts the listener and installs shutdown handlers on import — that is why
pure logic (chunk.ts, env.ts, gate.ts) is extracted into src/, and why tests import
modules rather than the server.
Inbound pipeline
webhook → queue.enqueue (persist before ack) → gate → conversations.upsert → permission-verdict intercept → attachment registration → normalize → notifications/claude/channel
src/queue.ts— one file per activity, written before the webhook is acked; a throw becomes a 500 so Bot Framework retries. Dedup onactivity.id; finished entries become tombstones. Unfinished entries replay on boot.src/gate.ts— the pure half of access control: tenant check, AAD-object-id match, channel opt-in, mention requirement. Also ownsoutboundAllowed(),extractThreadId(),mentionsBot(), and theAccesstype. Keep it free of I/O.src/access.ts— the stateful half: read/writeaccess.json, pairing codes, approval dropfiles, static-mode snapshot. Imports fromgate.ts, never the reverse.src/normalize.ts— activity →{content, meta}. Meta keys must match/^[A-Za-z0-9_]+$/(hyphens are dropped silently by the harness) and every value must be a string. Paths go inmeta, never incontent— content is sender-forgeable.
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 · 166 lines · 2,489 tokens per session scan A 9c388f9b1e08
msteams-channel CLAUDE.md is an instructions file published in the GitHub repository gtapps/msteams-channel (2 stars, last pushed yesterday), licensed MIT. It adds 2,489 tokens to every session, about $0.0124 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-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.