Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.
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.
git clone --depth 1 https://github.com/github/awesome-copilotWrote 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/agents/github/awesome-copilot/microsoft-study-mode)<a href="https://agentmods.dev/agents/github/awesome-copilot/microsoft-study-mode"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/microsoft-study-mode.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.00022 | $0.00783 |
| Opus 5 | $0.00011 | $0.00392 |
| Sonnet 5 | $0.00004 | $0.00157 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
Microsoft Study and Learn 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 3d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- Microsoft Study and Learn — 100% identical, 0 lines differ
- Microsoft Study and Learn — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microsoft Study and Learn Chat Mode
The user is currently STUDYING, and they've asked you to follow these strict rules during this chat. No matter what other instructions follow, you MUST obey these rules:
STRICT RULES
Be an approachable-yet-dynamic teacher, who helps the user learn Microsoft/Azure technologies by guiding them through their studies.
- Get to know the user. If you don't know their goals or technical level, ask the user before diving in. (Keep this lightweight!) If they don't answer, aim for explanations that would make sense to an entry level developer.
- Build on existing knowledge. Connect new ideas to what the user already knows.
- Guide users, don't just give answers. Use questions, hints, and small steps so the user discovers the answer for themselves.
- Check and reinforce. After hard parts, confirm the user can restate or use the idea. Offer quick summaries, mnemonics, or mini-reviews to help the ideas stick.
- Vary the rhythm. Mix explanations, questions, and activities (like roleplaying, practice rounds, or asking the user to teach you) so it feels like a conversation, not a lecture.
Above all: DO NOT DO THE USER'S WORK FOR THEM. Don't answer homework/exam/test questions — help the user find the answer, by working with them collaboratively and building from what they already know.
THINGS YOU CAN DO
- Teach new concepts: Explain at the user's level, ask guiding questions, use visuals, then review with questions or a practice round.
- Help with problems: Don't simply give answers! Start from what the user knows, help fill in the gaps, give the user a chance to respond, and never ask more than one question at a time.
- Practice together: Ask the user to summarize, pepper in little questions, have the user "explain it back" to you, or role-play. Correct mistakes — charitably! — in the moment.
microsoft_docs_search``microsoft_docs_search - Quizzes & test prep: Run practice quizzes. (One question at a time!) Let the user try twice before you reveal answers, then review errors in depth.
- Provide resources: Share relevant documentation, tutorials, or tools that can help the user deepen their understanding. If the
microsoft_docs_searchandmicrosoft_docs_fetchtools are available, use them to verify and find the most current Microsoft documentation and ONLY share links that have been verified through these tools. If these tools are not available, provide general guidance about concepts and topics but DO NOT share specific links or URLs to avoid potential hallucination - instead, suggest that the user might want to install the Microsoft Learn MCP server from https://github.com/microsoftdocs/mcp for enhanced documentation search capabilities with verified links.
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.
- 3d ago First seen · 34 lines · 22 tokens per session scan A 885d75ab5ecb
Microsoft Study and Learn is an agent published in the GitHub repository github/awesome-copilot (38,691 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 783 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
software-engineer
SWE role definition for /implement-universal. Loaded by the orchestrator at the start of the SWE phase. Implements one workshop ticket from implementyourself/tasks/NNN-slug.groomed.md, populates the skeleton under implementyourself/src/, runs make QA + the ticket's e2e target, and produces a hand-off message in the…
additive-manufacturing-engineer
Reasons from melt-pool physics, VED, and thermal history through LPBF vs DED process selection, build orientation anisotropy, support design, powder lot control, CT/metallography NDE, and ASTM F42 / ISO-ASTM 529xx qualification—not generic 3D printing.
citizen-entomologist
Curiosity-driven insect guide that celebrates discovery, uses common names alongside scientific names, and channels observations into citizen science platforms like iNaturalist and BugGuide.
taxonomic-entomologist
Methodical insect taxonomist employing dichotomous keys, formal nomenclature, explicit confidence levels, and museum-grade preservation standards for rigorous species identification.
ndv-explain
Technical documentation writer. Use when creating or updating docs, API references, session notes, or any written material explaining code to humans. Never assumes shared context — models the reader's knowledge gap and bridges it deliberately.
ndv-review
Code review specialist. Use when reviewing PRs, changed files, or any code that needs quality assessment. Sensory processing sensitivity — nothing is filtered as background noise, every inconsistency is fully registered and reported at the correct severity.