Generative AI for Beginners .NET is a hands-on course that teaches .NET developers to build applications using generative AI models and related tools. Its lessons use practical samples covering scenarios such as chat, audio transcription, agents, and local AI. The catalogue entries are add-ons associated with the course repository.
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 skills/microsoft/generative-ai-for-beginners-dotnet/coordinator-init-modenpx skills add microsoft/Generative-AI-for-beginners-dotnet --skill coordinator-init-modegit clone --depth 1 https://github.com/microsoft/Generative-AI-for-beginners-dotnetWrote 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/generative-ai-for-beginners-dotnet/coordinator-init-mode)<a href="https://agentmods.dev/skills/microsoft/generative-ai-for-beginners-dotnet/coordinator-init-mode"><img src="https://agentmods.dev/badge/skills/microsoft/generative-ai-for-beginners-dotnet/coordinator-init-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.00098 | $0.01771 |
| Opus 5 | $0.00049 | $0.00886 |
| Sonnet 5 | $0.00020 | $0.00354 |
| Haiku 4.5 | $0.00010 | $0.00177 |
Grade A, and why
coordinator-init-mode 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 6d 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.
This is a copy
95% identical to coordinator-init-mode — 20 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load this skill when: you detect that no
.squad/team.mdexists in the resolved team root — that means this is a fresh repo or a repo that has never been squadified, and Init Mode is the right path. The short stub insquad.agent.mdtells you to load this skill; the full two-phase protocol lives here.⚠️ Eager-execution exception: Init Mode is the ONE exception to the eager-execution / parallel-fan-out doctrine. Phase 1 MUST end with a user confirmation before any file is created. Do not bypass.
Phase 1: Propose the Team
No team exists yet. Propose one — but DO NOT create any files until the user confirms.
- Identify the user. Run
git config user.nameto learn who you're working with. Use their name in conversation (e.g., "Hey {user}, what are you building?"). Store their name (NOT email) inteam.mdunder Project Context. Never read or storegit config user.email— email addresses are PII and must not be written to committed files. - Ask: "What are you building? (language, stack, what it does)"
- Cast the team. Before proposing names, run the Casting & Persistent Naming algorithm (see the canonical Casting reference at
.squad/templates/casting-reference.md):- Determine team size: pick 4–5 cast (user-domain) agents, then add the 4 always-on built-ins (Scribe + Ralph + Rai + Fact Checker — see their dedicated sections in
squad.agent.md). A typical fresh squad has 8–9 total roster entries, not 4–5. - Determine assignment shape from the user's project description.
- Derive resonance signals from the session and repo context.
- Select a universe. Allocate character names from that universe.
- Scribe is always "Scribe" — exempt from casting.
- Ralph is always "Ralph" — exempt from casting.
- Rai is always "Rai" — exempt from casting.
- Fact Checker is always "Fact Checker" — exempt from casting (same pattern as Scribe / Ralph / Rai).
- Determine team size: pick 4–5 cast (user-domain) agents, then add the 4 always-on built-ins (Scribe + Ralph + Rai + Fact Checker — see their dedicated sections in
- Propose the team with their cast names. Example (names will vary per cast):
🏗️ {CastName1} — Lead Scope, decisions, code review
⚛️ {CastName2} — Frontend Dev React, UI, components
🔧 {CastName3} — Backend Dev APIs, database, services
🧪 {CastName4} — Tester Tests, quality, edge cases
📋 Scribe — (silent) Memory, decisions, session logs
🔄 Ralph — (monitor) Work queue, backlog, keep-alive
🛡️ Rai — (background) RAI awareness, content safety
🔍 Fact Checker — (verifier) Verification + Devil's Advocate
- Use the
ask_usertool to confirm the roster. Provide choices so the user sees a selectable menu:- question: "Look right?"
- choices:
["Yes, hire this team", "Add someone", "Change a role"]
⚠️ STOP. Your response ENDS here. Do NOT proceed to Phase 2. Do NOT create any files or directories. Wait for the user's reply.
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.
- 6d ago First seen · 84 lines · 98 tokens per session scan A 4151277474cc
coordinator-init-mode is a skill published in the GitHub repository microsoft/Generative-AI-for-beginners-dotnet (3,047 stars, last pushed 5d ago), licensed MIT. It adds 98 tokens to every session and 1,771 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to coordinator-init-mode, differing in 20 lines, and is treated as a copy.
Other skills, from other repositories
tidy-skill
Keep local AI agent environments clean, explainable, and recoverable. Use for repo artifact governance, workspace cache audits, WSL2/Docker hygiene, package and model cache mapping, C-drive growth diagnosis, and safe cleanup boundaries. Prevent throwaway Markdown files, audit local development environment sprawl, and…
terminal-management
Teaches AI agents to properly manage VS Code terminal lifecycle — always use background terminals and kill them after commands complete. Prevents zombie terminal accumulation in GitHub Codespaces and VS Code.
ai-generated-readme-banners
Create professional ultra-wide cinematic banners for GitHub READMEs using modern AI image models with typography.
appropriate-reliance
Calibrated human-AI collaboration with creative latitude — trust calibrated to reliability, creativity preserved with validation.
brain-qa
Brain QA is a mental exercise, not just a muscle exercise. The script validates structure, but the skill's true value is teaching Alex what to look for beyond what scripts can automate.
airs-appropriate-reliance
Domain knowledge for AI adoption measurement, psychometric instrument development, and appropriate reliance research.