agent-tools

Guidance for giving Microsoft Agent Framework agents tools, such as custom functions or supported built-in tools. Agent Framework is a software toolkit for building AI agents.

In plain words
What is it for?
Use it when creating agents with external functions, enabling built-in tools, or combining one agent as a tool for another.
Why use it?
It explains which agent types can accept tools and avoids assuming that every agent supports the same tool setup.

Agent for Codex

Install

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.

agentmods
npx agentmods add agents/managedcode/prompterone/agent-tools
Clone the repo
git clone --depth 1 https://github.com/managedcode/PrompterOne

Made for: Codex.

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,170 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.02170
Opus 5 $0.00004 $0.01085
Sonnet 5 $0.00002 $0.00434
Haiku 4.5 $0.00001 $0.00217

Measured yesterday against content hash 88453825fbc9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-tools 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.codex/skills/dotnet-microsoft-agent-framework/references/official-docs/user-guide/agents/agent-tools.md · 300 lines

How it starts

The opening of the file, as written. The whole thing — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Tools

[!NOTE] The live Learn tools surface now routes through https://learn.microsoft.com/agent-framework/agents/tools/overview. Current live docs also add a provider-support matrix and fold agent-as-tool composition into that broader tools overview.

Tooling support can vary considerably between different agent types. Some agents might allow developers to customize the agent at construction time by providing external function tools or by choosing to activate specific built-in tools that are supported by the agent. On the other hand, some custom agents might support no customization via providing external or activating built-in tools, if they already provide defined features that shouldn't be changed.

::: zone pivot="programming-language-csharp"

Therefore, the base abstraction does not provide any direct tooling support, however each agent can choose whether it accepts tooling customization at construction time.

Tooling support with ChatClientAgent

The ChatClientAgent is an agent class that can be used to build agentic capabilities on top of any inference service. It comes with support for:

  1. Using your own function tools with the agent
  2. Using built-in tools that the underlying service might support.

[!TIP] For more information on ChatClientAgent and information on supported services, see Simple agents based on inference services

Provide AIFunction instances during agent construction

There are various ways to construct a ChatClientAgent, for example, directly or via factory helper methods on various service clients, but all support passing tools.

// Sample function tool.
[Description("Get the weather for a given location.")]
static string GetWeather([Description("The location to get the weather for.")] string location)
    => $"The weather in {location} is cloudy with a high of 15°C.";

// When calling the ChatClientAgent constructor.
new ChatClientAgent(
    chatClient,
    instructions: "You are a helpful assistant",
    tools: [AIFunctionFactory.Create(GetWeather)]);

// When using one of the helper factory methods.
openAIResponseClient.AsAIAgent(
    instructions: "You are a helpful assistant",
    tools: [AIFunctionFactory.Create(GetWeather)]);

Read the full file on GitHub · 300 lines

Changes

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.

  1. yesterday First seen · 300 lines · 8 tokens per session scan A 88453825fbc9

Subscribe to this mod's changes

agent-tools is an agent published in the GitHub repository managedcode/PrompterOne (42 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 2,170 once invoked, about $0.0000 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.

Related

Other agents, from other repositories

release-manager

Owns the end-to-end modelcontextprotocol/csharp-sdk release process, orchestrating the prepare-release and publish-release skills (and the bump-version and breaking-changes skills they build on) across five stages: prepare (assess SemVer, bump the version, run ApiCompat/ApiDiff, review docs, draft release notes, open…

modelcontextprotocol/csharp-sdk · 317 tokens

wpf-data-binding-expert

WPF data binding specialist. Implements complex bindings (MultiBinding, PriorityBinding), custom converters, validation patterns, and debugging binding issues.

christian289/dotnet-with-claudecode · 34 tokens

wpf-control-designer

WPF CustomControl design and implementation specialist. Defines DependencyProperty, implements Parts and States Model, OnApplyTemplate patterns.

christian289/dotnet-with-claudecode · 30 tokens

serena-initializer

Serena MCP initialization agent. Checks if current project is activated and onboarded in Serena, performs activation and onboarding if not completed. Use when starting work on a new project or when Serena tools fail.

christian289/dotnet-with-claudecode · 46 tokens

theme-slot-auditor

Read-only auditor for Fluence.Wpf theming structure. Use after any theme, brush, color, accent, or ApplicationThemeManager change to verify the three-slot MergedDictionaries invariant, that slot [0] is rebuilt and replaced every Apply, DynamicResource usage, BrushFactory auto-twinning, canonical WinUI key names, and…

sintaxasn/Fluence.Wpf · 90 tokens

net472-feasibility-checker

Read-only checker that verifies new or changed code in Fluence.Wpf stays runnable on net472. Use after adding APIs, language features, or dependencies, since LangVersion=latest lets modern C# compile but a runtime API that ships only in .NET 10 fails on the separate net472 test lane. Enforces AGENTS.md section 4.3.

sintaxasn/Fluence.Wpf · 81 tokens