Borrowing it
Nothing to install: this file belongs to Maxim-Mazurok/teams-api. 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/Maxim-Mazurok/teams-api/main/.github/instructions/commit-message.instructions.mdgit clone --depth 1 https://github.com/Maxim-Mazurok/teams-apiWrote 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/maxim-mazurok/teams-api/commit-message)<a href="https://agentmods.dev/instructions/maxim-mazurok/teams-api/commit-message"><img src="https://agentmods.dev/badge/instructions/maxim-mazurok/teams-api/commit-message/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.
<a href="https://agentmods.dev/instructions/maxim-mazurok/teams-api/commit-message"><img src="https://agentmods.dev/badge/instructions/maxim-mazurok/teams-api/commit-message.svg" alt="Reviewed on agentmods" width="80" 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.00215 | $0.00215 |
| Opus 5.5 | $0.00086 | $0.00086 |
| Sonnet 5.5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00021 | $0.00021 |
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 1mo 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.
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, andrevert. - Choose
featonly for user-visible or API-visible functionality changes. - Use
fixfor bug fixes. - Use
docs,ci,test,refactor,build,style,perf,revert, orchorewhen 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 aBREAKING CHANGE:footer that explains the compatibility impact.
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.
- 1mo ago First seen · 14 lines · 215 tokens per session scan A 764a1f52408b
teams-api commit-message.instructions.md is an instructions file published in the GitHub repository Maxim-Mazurok/teams-api (8 stars, last pushed 5d ago), licensed MIT. It adds 215 tokens to every session, about $0.0009 per session on Opus 5.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
skill-doctor github-automation.instructions.md
Instructions for evilstar2016/skill-doctor, covering github-automation, description, when to use and instructions.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).