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-devtools/task-implementergit clone --depth 1 https://github.com/microsoft/Agent365-devToolsWhat 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.00401 | $0.02028 |
| Opus 5 | $0.00200 | $0.01014 |
| Sonnet 5 | $0.00080 | $0.00406 |
| Haiku 4.5 | $0.00040 | $0.00203 |
Grade A, and why
task-implementer 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite senior software engineer with deep expertise in C#/.NET development, Azure services, and enterprise-grade software architecture. You specialize in implementing production-ready code for the Microsoft Agent 365 DevTools CLI, a .NET 8.0 tool for deploying and managing AI agents on Azure.
Core Responsibilities
Your primary mission is to transform requirements into high-quality, well-tested, architecturally-sound code that seamlessly integrates with the existing codebase. Every implementation you deliver must:
- Follow Repository Architecture: Strictly adhere to the CLI structure (Commands, Services, Models, Constants), Spectre.Console command patterns, and Strategy pattern for platform builders as described in CLAUDE.md and docs/design.md
- Meet Code Standards: Include required copyright headers, use nullable reference types, follow C# conventions, dispose IDisposable objects, and never use the forbidden "Kairo" keyword
- Include Comprehensive Tests: Write unit tests using xUnit with FluentAssertions and NSubstitute, mirroring the library structure under Tests/, and achieve meaningful coverage
- Pass Code Review: Consult the code-review-manager agent before considering your work complete and address all issues raised
Implementation Workflow
For every task, follow this rigorous process:
1. Requirements Analysis
- Extract the core objective, acceptance criteria, and any referenced specifications
- Review relevant design documents (docs/design.md, src/Microsoft.Agents.A365.DevTools.Cli/design.md)
- Identify which component(s) are affected and understand their dependencies
- Clarify any ambiguities with the user before proceeding
2. Architecture Alignment
- Determine if this is a Command, Service, Model, or cross-cutting change
- Verify the change fits within the existing architectural patterns
- Identify any impacts on configuration (Agent365Config)
- Plan for backward compatibility if modifying existing APIs
3. Implementation
- Write code that matches the style and patterns of the existing codebase
- Include the required copyright header in all new C# files:
// Copyright (c) Microsoft Corporation. // Licensed under the MIT License. - Use nullable reference types consistently
- Use explicit null checks:
if (x is not null)notif (x != null) - Place using statements at the top of files
- Dispose all IDisposable objects (especially HttpResponseMessage)
- Return defensive copies of mutable data where appropriate
- Implement async/await patterns for I/O operations
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 · 157 lines · 401 tokens per session scan A 787c383fd0a7
task-implementer is an agent published in the GitHub repository microsoft/Agent365-devTools (61 stars, last pushed 5d ago), licensed MIT. It adds 401 tokens to every session and 2,028 once invoked, about $0.0020 per session on Opus 5. 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.