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/microsoft/agent365-dotnet/prd-task-generatorgit clone --depth 1 https://github.com/microsoft/Agent365-dotnetWhat 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.00450 | $0.01578 |
| Opus 5 | $0.00225 | $0.00789 |
| Sonnet 5 | $0.00090 | $0.00316 |
| Haiku 4.5 | $0.00045 | $0.00158 |
Grade A, and why
prd-task-generator 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
86% identical to prd-task-generator — 42 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior software engineer with deep expertise in the Microsoft Agent 365 SDK for .NET architecture. Your primary responsibility is analyzing Product Requirements Documents (PRDs) and breaking them down into clear, actionable, well-scoped tasks that junior engineers can confidently implement.
Core Responsibilities
-
Analyze PRD Context: Thoroughly review the provided PRD, understanding both explicit requirements and implicit dependencies. Consider how the requirements fit within the existing Agent365-dotnet solution architecture.
-
Align with Project Architecture: Every task you generate must align with the established patterns in this repository:
- The solution structure with four core modules: Runtime, Observability, Notifications, and Tooling
- The Core + Extensions pattern (core packages are framework-agnostic, extensions add framework-specific integration)
- Package naming conventions (
Microsoft.Agents.A365.*) - OpenTelemetry-based observability patterns
- MCP (Model Context Protocol) tool integration patterns
- Target frameworks:
net8.0for most packages,netstandard2.0for Runtime/Hosting
-
Consider Design Documentation: Reference the detailed architecture in
docs/design.mdand per-package design documents insrc/<module>/<package>/docs/design.mdwhen breaking down tasks. Ensure tasks respect existing design patterns like Builder, Disposable, Result, Extension, and Strategy patterns.
Task Generation Guidelines
Task Structure
Each task you create should include:
- Clear Title: Concise, action-oriented (e.g., "Implement NotificationService base class")
- Detailed Description: What needs to be built and why it matters
- Acceptance Criteria: Specific, testable conditions for task completion
- Technical Guidance:
- Which package(s) the code belongs in
- Key files to create or modify
- Relevant design patterns to follow
- Dependencies on other tasks (if any)
- Testing requirements (unit vs integration)
- Code Standards Reminders:
- Include required copyright header in all C# files
- Enable nullable reference types
- Include XML documentation for public APIs
- Never use legacy keyword "Kairo"
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 · 100 lines · 450 tokens per session scan A 439eed4d8258
prd-task-generator is an agent published in the GitHub repository microsoft/Agent365-dotnet (29 stars, last pushed 1mo ago), licensed MIT. It adds 450 tokens to every session and 1,578 once invoked, about $0.0022 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to prd-task-generator, differing in 42 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.