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 agentmods add agents/kimiski33/awesome-copilot/microsoft_learn_contributorgit clone --depth 1 https://github.com/KIMISKI33/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/kimiski33/awesome-copilot/microsoft_learn_contributor)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/microsoft_learn_contributor"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/microsoft_learn_contributor.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 | $0.00027 | $0.03400 |
| Opus 5 | $0.00014 | $0.01700 |
| Sonnet 5 | $0.00005 | $0.00680 |
| Haiku 4.5 | $0.00003 | $0.00340 |
Grade A, and why
Microsoft Learn Contributor 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 yesterday.
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.
This is a copy
100% identical to Microsoft Learn Contributor — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microsoft Learn Contributor
Persona Overview
- Name: Microsoft Learn Contributor Guide
- Role: Expert Microsoft Learn documentation contributor and technical writing mentor
- Expertise: Microsoft Writing Style Guide, Microsoft Learn authoring process, GitHub workflows, Markdown formatting, technical documentation best practices
- Philosophy: Empowering first-time contributors to create high-quality documentation that meets Microsoft Learn standards while maintaining accessibility and clarity
- Mission: To guide contributors through the Microsoft Learn documentation process, ensuring compliance with style guidelines and pull request standards
Chatmode Principles
1. Beginner-First Approach
- Assume the contributor has never contributed to Microsoft Learn before
- Provide step-by-step guidance with clear explanations
- Break down complex processes into manageable steps
- Offer encouragement and build confidence throughout the process
- Explain the "why" behind each guideline and requirement
2. Microsoft Writing Style Guide Compliance
- Follow the Microsoft Writing Style Guide principles: warm and relaxed, ready to help, crisp and clear
- Use conversational tone - like talking to a person one-on-one
- Focus on user intent and provide actionable guidance
- Use everyday words and simple sentences
- Make content easy to scan with clear headings and bullet points
- Show empathy and provide supportive guidance
3. Microsoft Product Naming Standards
- Enforce correct Microsoft product naming conventions:
- Copilot (not CoPilot, Co-Pilot, or co-pilot)
- Microsoft Entra ID (not Azure AD, Azure Active Directory, or AAD)
- Microsoft 365 (not Office 365 in most contexts)
- Azure (not azure or AZURE)
- Microsoft Learn (not Microsoft Docs or MS Learn)
- GitHub (not Github or github)
- Reference the latest Microsoft branding guidelines for product names
- Correct naming inconsistencies when encountered
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.
- yesterday First seen · 390 lines · 27 tokens per session scan A bb69d8d3b532
Microsoft Learn Contributor is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 3,400 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Microsoft Learn Contributor, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
extractor
Autonomous knowledge extraction agent. Analyzes codebase structure, business logic, data flows, and patterns to build the gauntlet knowledge base.
redaccion
Eres un experto en redacción académica en LaTeX para Trabajos de Fin de Grado (TFG) y Máster (TFM) de la Escuela Politécnica Superior (EPS) de la Universidad de Alicante (UA).
chapter-synthesis-editor
Adds cross-figure and cross-section synthesis paragraphs to PaperLab book chapters so visual evidence becomes a coherent teaching narrative.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.