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.
Borrowing it
Nothing to install: this file belongs to microsoft/Generative-AI-for-beginners-dotnet. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/Generative-AI-for-beginners-dotnet/main/.github/skills/coordinator-response-mode/SKILL.mdgit 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-response-mode)<a href="https://agentmods.dev/skills/microsoft/generative-ai-for-beginners-dotnet/coordinator-response-mode"><img src="https://agentmods.dev/badge/skills/microsoft/generative-ai-for-beginners-dotnet/coordinator-response-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.00079 | $0.01172 |
| Opus 5 | $0.00039 | $0.00586 |
| Sonnet 5 | $0.00016 | $0.00234 |
| Haiku 4.5 | $0.00008 | $0.00117 |
Grade A, and why
coordinator-response-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 8d 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
100% identical to coordinator-response-mode — 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load this skill when: you have routed work to an agent and need to pick the response mode (Direct / Lightweight / Standard / Full). The 1-line stub in
squad.agent.mdis for awareness; this skill is the full decision table + templates.
Response Mode Selection
After routing determines WHO handles work, select the response MODE based on task complexity. Bias toward upgrading — when uncertain, go one tier higher rather than risk under-serving.
| Mode | When | How | Target |
|---|---|---|---|
| Direct | Status checks, factual questions the coordinator already knows, simple answers from context | Coordinator answers directly — NO agent spawn | ~2-3s |
| Lightweight | Single-file edits, small fixes, follow-ups, simple scoped read-only queries | Spawn ONE agent with minimal prompt (see Lightweight Spawn Template below). Use agent_type: "explore" for read-only queries |
~8-12s |
| Standard | Normal tasks, single-agent work requiring full context | Spawn one agent with full ceremony — charter inline, history read, decisions read. This is the current default | ~25-35s |
| Full | Multi-agent work, complex tasks touching 3+ concerns, "Team" requests | Parallel fan-out, full ceremony, Scribe included | ~40-60s |
Direct Mode exemplars
Coordinator answers instantly, no spawn:
- "Where are we?" → Summarize current state from context: branch, recent work, what the team's been doing. A user favorite — make it instant.
- "How many tests do we have?" → Run a quick command, answer directly.
- "What branch are we on?" →
git branch --show-current, answer directly. - "Who's on the team?" → Answer from
team.mdalready in context. - "What did we decide about X?" → Answer from
decisions.mdalready in context.
Lightweight Mode exemplars
One agent, minimal prompt:
- "Fix the typo in README" → Spawn one agent, no charter, no history read.
- "Add a comment to line 42" → Small scoped edit, minimal context needed.
- "What does this function do?" →
agent_type: "explore"(Haiku model, fast). - Follow-up edits after a Standard/Full response — context is fresh, skip ceremony.
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.
- 8d ago First seen · 98 lines · 79 tokens per session scan A 9e022fe051a6
coordinator-response-mode is a skill published in the GitHub repository microsoft/Generative-AI-for-beginners-dotnet (3,051 stars, last pushed 7d ago), licensed MIT. It adds 79 tokens to every session and 1,172 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to coordinator-response-mode, differing in 0 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.
azure-ml-model-evaluation
Evaluate generative AI applications and models locally or in the cloud using Azure AI Evaluation SDK. Measure quality, safety, and performance with built-in and custom evaluators.
azure-ml-dataset-creator
Generate synthetic and simulated datasets for evaluation and fine-tuning using Azure AI Foundry simulators. Create non-adversarial task data, adversarial safety data, and conversation datasets without manual data collection.
azure-ml-llm-trainer
Train or fine-tune LLMs on Azure ML managed compute with TRL trainers. Uses direct trainer loops (SFT, DPO, RL) without relying on serverless APIs or Hugging Face infrastructure.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.