agentmods.dev

teams-api commit-message.instructions.md

Commit-message rules for the teams-api project, which connects Microsoft Teams to an API for reading conversations, sending messages, and managing members.

In plain words
What is it for?
Use them when writing commits, especially to choose a Conventional Commits type and handle breaking changes.
Why use it?
They keep commit messages consistent and make the type and scope of each change clear.

Instructions file for GitHub Copilot

5 5d ago A scan 215 tokens original MIT
View the source file Maxim-Mazurok/teams-api
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.

agentmods
npx agentmods add instructions/maxim-mazurok/teams-api/commit-message
Clone the repo
git clone --depth 1 https://github.com/Maxim-Mazurok/teams-api

Made for: GitHub Copilot.

Per session 215 This file is loaded in full into every session.
When invoked 215 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00215 $0.00215
Opus 5 $0.00108 $0.00108
Sonnet 5 $0.00043 $0.00043
Haiku 4.5 $0.00021 $0.00021

Measured 2d ago against content hash 764a1f52408b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

teams-api commit-message.instructions.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 2d 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.

.github/instructions/commit-message.instructions.md · 14 lines

What it actually says

Commit Message Instructions

  • Generate commit messages using Conventional Commits.
  • Format the subject as <type>: <summary>.
  • Allowed types are feat, fix, docs, chore, ci, refactor, test, style, build, perf, and revert.
  • Choose feat only for user-visible or API-visible functionality changes.
  • Use fix for bug fixes.
  • Use docs, ci, test, refactor, build, style, perf, revert, or chore when those better match the staged changes.
  • Keep the summary in imperative mood and lowercase after the colon.
  • Keep the subject focused on the staged diff only.
  • Do not mention AI, Copilot, or tooling in the commit message.
  • Do not add a body unless the staged changes are breaking.
  • For breaking changes, use the subject <type>!: <summary> and add a BREAKING CHANGE: footer that explains the compatibility impact.
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. 2d ago First seen · 14 lines · 215 tokens per session scan A 764a1f52408b

Subscribe to this mod's changes

teams-api commit-message.instructions.md is an instructions file published in the GitHub repository Maxim-Mazurok/teams-api (5 stars, last pushed 5d ago), licensed MIT. It adds 215 tokens to every session, about $0.0011 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.

Backend and APIsGit and workflowWriting and docsclimcpms-team-automationsms-teamsms-teams-apiteams
Related

Other instructions, from other repositories

teams-mcp copilot-instructions.md

Instructions for floriscornel/teams-mcp, covering copilot instructions — teams-mcp, project overview, architecture, commands and ci/cd.

floriscornel/teams-mcp · 1,680 tokens

chat AGENTS.md

AGENTS.md instructions for vercel/chat, covering agents.md, commands, per-package, monorepo layout and architecture.

vercel/chat · 1,279 tokens

vexa AGENTS.md

AGENTS.md instructions for Vexa-ai/vexa, covering agents.md — the agent front door (in-repo), researching vexa? start here, driving vexa from an agent session, your issue is your prd and claiming — and say hello on discord.

Vexa-ai/vexa · 3,110 tokens

vexa CLAUDE.md

Claude Code instructions for Vexa-ai/vexa, a project described as: Open-source meeting transcription API for Google Meet, Microsoft Teams & Zoom. Auto-join bots, real-time WebSocket transcripts, MCP server for AI agents. Self-host or use hosted SaaS.

Vexa-ai/vexa · 132 tokens

agent-almanac CLAUDE.md

Instructions for pjt222/agent-almanac, covering claude.md, project overview, architecture, five content types and registries.

pjt222/agent-almanac · 12,301 tokens

operately copilot-instructions.md

Copilot instructions for operately/operately, covering operately development instructions, pull request naming convention, working effectively, bootstrap and build the repository and prerequisites: docker 20.0+ with compose plugin, make 4.0+.

operately/operately · 4,451 tokens