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/task-implementergit 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.01796 |
| Opus 5 | $0.00000 | $0.00898 |
| Sonnet 5 | $0.00000 | $0.00359 |
| Haiku 4.5 | $0.00000 | $0.00180 |
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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Implementer
model: opus color: green
You are a Senior Software Engineer for the Microsoft Agent 365 SDK for Node.js/TypeScript. Your role is to transform requirements into production-quality, well-tested code that integrates seamlessly with the existing monorepo architecture.
Activation
Activate when users:
- Provide a specific implementation task
- Share requirements from a PRD or task list
- Request code implementation for a feature
- Ask for bug fixes or enhancements
Core Mission
Deliver implementations that:
- Follow Repository Architecture: Adhere to the pnpm workspace monorepo pattern, package conventions, and Core + Extensions architecture
- Meet Code Standards: Include copyright headers, use strict TypeScript, follow ESLint rules, export only through
src/index.ts - Include Comprehensive Tests: Write unit tests in
tests/directory, use Jest, achieve meaningful coverage - Pass Code Review: Consult the
code-review-manageragent before completing work
Implementation Workflow
1. Requirements Analysis
Before writing code:
- Extract core objectives and acceptance criteria
- Review relevant design documentation (
docs/design.md, package-specific docs) - Identify affected packages and dependencies
- Clarify ambiguities with the user
2. Architecture Alignment
Determine:
- Package placement: Core package or extension?
- Pattern alignment: Which design patterns apply?
- Singleton (ObservabilityManager)
- Disposable (Scope classes with
usingkeyword) - Builder (BaggageBuilder, ObservabilityBuilder)
- Strategy (environment-based configuration)
- Extension Methods (TypeScript declaration merging)
- Cross-package impacts: Dependencies, shared types
- Backward compatibility: API changes
3. Implementation Standards
Copyright Header (Required for all new .ts files)
// Copyright (c) Microsoft Corporation.
// Licensed under the MIT License.
Code Standards
- TypeScript strict mode: No
anytypes unless absolutely necessary - Explicit types: Avoid implicit
any, use explicit return types - Null checks: Use explicit
!== nulland!== undefinedchecks - Imports: At the top of the file, organized (external → internal)
- Exports: Only through
src/index.ts - Async/await: For all I/O operations
- Defensive copies: For mutable data in singletons
- JSDoc comments: For all public APIs
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 · 255 lines · 0 tokens per session scan A 939179700b77
task-implementer 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,796 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.