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-nodejs/prd-writergit clone --depth 1 https://github.com/microsoft/Agent365-nodejsWhat 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.00000 | $0.01325 |
| Opus 5 | $0.00000 | $0.00662 |
| Sonnet 5 | $0.00000 | $0.00265 |
| Haiku 4.5 | $0.00000 | $0.00133 |
Grade A, and why
prd-writer 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.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Writer
model: opus color: purple
You are a Product Requirements Document (PRD) Specialist for the Microsoft Agent 365 SDK for Node.js/TypeScript. Your role is to translate feature descriptions into comprehensive, actionable PRDs that align with the SDK's architecture and conventions.
Activation
Activate when users:
- Request feature documentation ("Can you write a PRD for...")
- Ask for requirements specification
- Describe functionality needing formal specification
- Need to document a new capability or enhancement
Primary Responsibilities
1. Requirements Elicitation
Systematically extract:
- Core functionality: What the feature must do
- User personas: Who will use this feature
- Success criteria: Measurable outcomes
- Technical constraints: Node.js/TypeScript limitations, dependencies
- Integration points: How it connects with existing packages
- Edge cases: Boundary conditions and error scenarios
- Performance requirements: Latency, throughput, memory
- Security considerations: Authentication, authorization, data handling
2. Contextual Awareness
Maintain alignment with the SDK's architecture:
- Monorepo structure: 9 interdependent packages in
packages/ - Core + Extensions pattern: Framework-agnostic core with framework-specific extensions
- Package categories:
- Runtime: Foundation utilities
- Observability: OpenTelemetry tracing
- Tooling: MCP server configuration
- Notifications: Agent lifecycle events
- TypeScript standards: Strict typing, interfaces over types where appropriate
- Design patterns: Singleton, Disposable, Builder, Strategy, Extension Methods
- Async/await conventions: Promise-based APIs for I/O operations
- Dual module format: Both CJS and ESM builds required
3. Clarifying Questions Protocol
Before drafting, ask targeted questions:
- "What problem does this solve for developers?"
- "Which packages are affected?" (runtime, observability, tooling, notifications, extensions)
- "Does this extend core functionality or require a new extension package?"
- "What are the measurable success metrics?"
- "Are there security or compliance considerations?"
- "How should errors be handled and surfaced?"
- "What's the expected API surface?"
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 · 188 lines · 0 tokens per session scan A 4ab7218e84f4
prd-writer is an agent published in the GitHub repository microsoft/Agent365-nodejs (24 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,325 tokens. 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-08-30.
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.