What is m365-copilot-companion-mcp AGENTS.md?

Repository instructions for an MCP companion project, including a rule that work needed on another computer must be merged into the main branch and pushed to the shared repository.

They are for guiding branch work, pull requests, CI and security checks, merging, pushing, and confirming that another computer can use the completed change.

They prevent a fix from being treated as delivered when it exists only on a feature branch or when the main branch is failing. They also require checking the final main-branch workflow results.

How MasayukiTa/m365-copilot-companion-mcp configures Codex and OpenCod

Reuse

Borrowing it

Nothing to install: this file belongs to MasayukiTa/m365-copilot-companion-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/MasayukiTa/m365-copilot-companion-mcp/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/MasayukiTa/m365-copilot-companion-mcp

Made for: Codex, OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/masayukita/m365-copilot-companion-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/masayukita/m365-copilot-companion-mcp/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/masayukita/m365-copilot-companion-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/masayukita/m365-copilot-companion-mcp/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/masayukita/m365-copilot-companion-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/masayukita/m365-copilot-companion-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 450 This file is loaded in full into every session.

When invoked 450 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00450	$0.00450
Opus 5.5	$0.00180	$0.00180
Sonnet 5.5	$0.00090	$0.00090
Haiku 4.5	$0.00045	$0.00045

Measured 1mo ago against content hash 9c0fab51b257, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

m365-copilot-companion-mcp AGENTS.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.

AGENTS.md · 31 lines

What it actually says

Repository agent rules

Cross-PC delivery rule

A feature branch is staging, not delivery. Any fix or operational change that must be available on another PC is not complete until it is merged into main and pushed to origin/main.

For cross-PC / production-relevant fixes:

Develop and test on a branch.
Push the branch and open a PR to main so CI, Windows build, CodeQL, secret scan, and applicable workflow checks run.
Do not merge while required checks are failing or while the working tree contains unrelated changes.
Merge to main only after the change is stable enough to be the repository's portable baseline.
Verify the merged commit is present on origin/main; a branch-only push does not make the change available to another PC.
After merge, inspect the main workflow runs. A green feature branch with a red main is not a finished delivery.

Do not postpone this integration step when the current work is specifically about stability, setup, portability, authentication, fleet scheduling, or anything needed on a second machine.

Temporary files: one swept home

Everything temporary that this product or an agent creates goes under %TEMP%\m365-companion\ (relay/temp_home.py: temp_home(), temp_dir(name)). relay/fleet_retention.py (sweep_temp_home, run by apply()) deletes entries there that have had no write for 24 hours (override with the env var MCP_TEMP_HOME_MAX_AGE_H). Nothing else in %TEMP% is ever swept.

Put venvs, clones, build output and test scratch under %TEMP%\m365-companion\agents\<name>\ and delete them when the work is done; the sweep is the backstop, not the plan.
An idle directory is judged by its newest file. A long-lived venv you still need must be touched (or used) at least once a day, or put somewhere else.
Do not write new scratch directly in %TEMP%: it is not swept and was the cause of the disk filling up.

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.

1mo ago Changed · +15 lines · +220 tokens per session 9c0fab51b257
1mo ago First seen · 16 lines · 230 tokens per session scan A 83906a8ba8a2

Subscribe to this mod's changes

m365-copilot-companion-mcp AGENTS.md is an instructions file published in the GitHub repository MasayukiTa/m365-copilot-companion-mcp (11 stars, last pushed yesterday), licensed MIT. It adds 450 tokens to every session, about $0.0018 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-09-29.

CI and CD DevOps and cloud Git and workflow agent automation claude copilot-studio fastmcp local-first

m365-copilot-companion-mcp AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
m365-copilot-companion-mcp AGENTS.mdMasayukiTa/m365-copilot-companion-mcp	Instructions file	11	yesterday	MIT	A	450	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

m365-copilot-companion-mcp: Instructions file for Codex