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 instructions/dotnet/maui-labs/mcp-toolsgit clone --depth 1 https://github.com/dotnet/maui-labsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/dotnet/maui-labs/mcp-tools)<a href="https://agentmods.dev/instructions/dotnet/maui-labs/mcp-tools"><img src="https://agentmods.dev/badge/instructions/dotnet/maui-labs/mcp-tools.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01338 | $0.01338 |
| Opus 5 | $0.00669 | $0.00669 |
| Sonnet 5 | $0.00268 | $0.00268 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade A, and why
maui-labs mcp-tools.instructions.md 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 5d ago.
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Tool Development Guide
Adding a New MCP Tool
Step 1: Create the Tool File
Create src/Cli/Microsoft.Maui.Cli/DevFlow/Mcp/Tools/MyNewTool.cs:
using System.ComponentModel;
using ModelContextProtocol;
using ModelContextProtocol.Server;
using ModelContextProtocol.Protocol;
using Microsoft.Maui.Cli.DevFlow.Mcp;
namespace Microsoft.Maui.Cli.DevFlow.Mcp.Tools;
[McpServerToolType]
public sealed class MyNewTool
{
[McpServerTool(Name = "maui_my_action"),
Description("Clear, complete description of what this tool does. Mention when an AI agent should use it.")]
public static async Task<string> MyAction(
McpAgentSession session,
[Description("Describe what this parameter controls")] string requiredParam,
[Description("Describe this optional parameter and its default behavior")] bool optionalFlag = false,
[Description("Agent HTTP port (optional if only one agent connected)")] int? agentPort = null)
{
var agent = await session.GetAgentClientAsync(agentPort);
// Call agent.* methods to interact with the running app
var result = await agent.SomeMethodAsync(requiredParam);
return result ?? "No result";
}
}
Step 2: Register the Tool
Add to src/Cli/Microsoft.Maui.Cli/DevFlow/Mcp/McpServerHost.cs:
.WithTools<MyNewTool>()
Step 3: Add the Corresponding AgentClient Method (if needed)
If the tool calls a new agent endpoint, add the client method in Microsoft.Maui.DevFlow.Client/AgentClient.cs.
Naming Conventions
- Tool names:
maui_prefix + snake_case action:maui_screenshot,maui_tap,maui_network - Class names: PascalCase with a
ToolorToolssuffix:ScreenshotTool,InteractionTools,NetworkTool - Use plural
*Toolswhen grouping multiple related actions in one file (e.g.,InteractionToolshas tap, fill, clear) - One file can contain multiple related tools (e.g.,
InteractionToolshas tap, fill, clear)
Parameter Rules
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.
- 5d ago First seen · 100 lines · 1,338 tokens per session scan A bb48f7404c81
maui-labs mcp-tools.instructions.md is an instructions file published in the GitHub repository dotnet/maui-labs (212 stars, last pushed yesterday), licensed MIT. It adds 1,338 tokens to every session, about $0.0067 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 instructions, from other repositories
react-native-restart AGENTS.md
Instructions for avishayil/react-native-restart: This project keeps its agent/AI onboarding guidance in a single canonical file.
AppClaw CLAUDE.md
Claude Code instructions for appclawhq/AppClaw, covering claude.md, what is appclaw?, build & run commands, architecture and entry point & cli modes (src/index.ts).
expo-targets AGENTS.md
AGENTS.md instructions for csark0812/expo-targets, covering agents, product posture, sealed zones, docs ssot and safe commands.
OpenNutriTracker CLAUDE.md
Claude Code instructions for simonoppowa/OpenNutriTracker: Canonical agent instructions for this repository live in AGENTS.md.
nc-native AGENTS.md
AGENTS.md instructions for Obiente/nc-native, covering nextcloud native agent and contributor guide, 1. mission and current phase, 2. sources of truth, documentation synchronization and 3. what "native" means.
unity-cross-platform-local-build-orchestrator AGENTS.md
Instructions for sinanata/unity-cross-platform-local-build-orchestrator, covering agents.md, what this project is, golden rules (do not violate), use it and interface.