microsoft/copilot-camp is a collection of hands-on workshops for extending Microsoft 365 Copilot and building custom engine agents. Developers use it to learn how to create declarative agents, connectors, MCP servers, multi-agent workflows, API integrations, and other Copilot extensions. The catalogue entries are skills and instructions for these development workflows.
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.
npx skills add microsoft/copilot-camp --skill weekly-status-mailgit clone --depth 1 https://github.com/microsoft/copilot-campWrote 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/skills/microsoft/copilot-camp/weekly-status-mail)<a href="https://agentmods.dev/skills/microsoft/copilot-camp/weekly-status-mail"><img src="https://agentmods.dev/badge/skills/microsoft/copilot-camp/weekly-status-mail/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/skills/microsoft/copilot-camp/weekly-status-mail"><img src="https://agentmods.dev/badge/skills/microsoft/copilot-camp/weekly-status-mail.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00133 | $0.01119 |
| Opus 5.5 | $0.00053 | $0.00448 |
| Sonnet 5.5 | $0.00027 | $0.00224 |
| Haiku 4.5 | $0.00013 | $0.00112 |
Grade A, and why
weekly-status-mail 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Produces a short, scannable weekly status email addressed to the user's team. It gathers the user's open tasks, upcoming meetings, and outstanding action items from Microsoft 365, then composes a friendly email with emoji section headers and saves it as a draft for review — it never sends automatically.
When to Use
- The user wants their recurring weekly status note to their team.
- The user asks to "recap this week" or "write my Monday update" for the team.
- The user wants open tasks, upcoming meetings, and action items rolled into one email.
When NOT to Use
- Updates aimed at leadership, executives, or cross-functional stakeholders — use stakeholder-comms instead.
- One-off announcements, replies, or any non-status email — use the Outlook tools directly.
- A status document or spreadsheet rather than an email — use docx or xlsx.
Quick Start
User: "Draft my weekly status email for the team"
1. Resolve the week window (today → next 7 days) and the team recipients.
2. Gather: open tasks, upcoming meetings, action items from M365.
3. Compose the email body with emoji section headers (concise bullets).
4. Save as a draft with CreateDraftMessage and show it for review.
Core Instructions
Step 1: Resolve recipients and time window
- Determine the week window: today through the next 7 days, in the user's local time zone.
- Resolve "the team" with people tools —
GetDirectReportsDetailsfor the user's reports, or a team distribution list the user names. Never guess email addresses. - If the team cannot be resolved, draft anyway with an empty To line and a clear
[Add team recipients]note, and flag it for the user.
Step 2: Gather open tasks
- Use
SearchM365(sources: email, teams) for open/pending work, andListMessageswithflagged_only=truefor follow-up flags. - Include only items found in tool results. If none are found, write "Nothing outstanding to report."
Step 3: Gather upcoming meetings
- Call
ListCalendarViewfor the next 7 days; list notable meetings with day and time. - Respect privacy: render
private/confidentialevents as "Busy" or a time block — do not echo their subject lines.
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 · 100 lines · 133 tokens per session scan A e8e332067c1b
weekly-status-mail is a skill published in the GitHub repository microsoft/copilot-camp (671 stars, last pushed yesterday), licensed MIT. It adds 133 tokens to every session and 1,119 once invoked, about $0.0005 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-30.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…