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/ufo/overviewgit clone --depth 1 https://github.com/microsoft/UFOWhat 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.06260 |
| Opus 5 | $0.00000 | $0.03130 |
| Sonnet 5 | $0.00000 | $0.01252 |
| Haiku 4.5 | $0.00000 | $0.00626 |
Grade A, and why
overview 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 — 813 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Device Agent Architecture
Device Agents are the execution engines of UFO3's multi-device orchestration system. Each device agent operates as an autonomous, intelligent controller that translates high-level user intentions into low-level system commands. The architecture is designed for extensibility, safety, and scalability across heterogeneous computing environments.
Overview
UFO3 orchestrates tasks across multiple devices through a network of Device Agents. Originally designed as a Windows automation framework (UFO2), the architecture has evolved to support diverse platforms including Linux, macOS, and embedded systems. This document describes the abstract design principles and interfaces that enable this multi-platform capability.
Key Capabilities:
- Multi-Platform: Windows agents (HostAgent, AppAgent), Linux agent, extensible to macOS and embedded systems
- Safe Execution: Server-client separation isolates reasoning from system-level operations
- Scalable Architecture: Hierarchical agent coordination supports complex cross-device workflows
- LLM-Driven Reasoning: Dynamic decision-making using large language models
- Modular Design: Three-layer architecture (State, Strategy, Command) enables customization
Three-Layer Architecture
Device agents implement a three-layer framework that separates concerns, promotes modularity, and enables extensibility:
graph TB
subgraph "Device Agent Architecture"
subgraph "Level-1: State Layer (FSM)"
S1[AgentState]
S2[State Machine]
S3[State Transitions]
S1 --> S2 --> S3
end
subgraph "Level-2: Strategy Layer (Execution Logic)"
P1[ProcessorTemplate<br/>Strategy Orchestrator]
P2[DATA_COLLECTION<br/>Strategies]
P3[LLM_INTERACTION<br/>Strategies]
P4[ACTION_EXECUTION<br/>Strategies]
P5[MEMORY_UPDATE<br/>Strategies]
P1 -->|manages & executes| P2
P2 --> P3 --> P4 --> P5
end
subgraph "Level-3: Command Layer (System Interface)"
C1[CommandDispatcher]
C2[MCP Tools]
C3[Atomic Commands]
C1 --> C2 --> C3
end
S3 -->|delegates to| P1
P5 -->|executes via| C1
end
LLM[Large Language Model]
P3 -.->|reasoning| LLM
LLM -.->|decisions| P4
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 · 813 lines · 0 tokens per session scan A d74bb2044df1
overview is an agent published in the GitHub repository microsoft/UFO (9,589 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,260 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
mobile
Use for mobile app development, React Native, Flutter, iOS, Android, and cross-platform mobile tasks.
builder
Turn shot-plan.json into one renderable HyperFrames composition (compositions/index.html). Everything stays in the HF ecosystem — HTML is the source of truth; a single paused GSAP timeline carries all motion; the engine seeks it. Category-specific build rules live in categories/ /module.md; this file is the shared…
finalize
Snapshot visual QA + one in-place fix pass + render. Dispatched only when Step 6 lint/inspect reports issues, or to do the final render.
godot-csharp-engineer
Use this agent for C#-first Godot 4.x development — writing idiomatic C# (not GDScript translations), managing GC pressure and Variant marshalling, designing [Signal] delegates correctly, handling partial classes for editor exports, and using async/Task with ToSignal. Also use this agent in parity mode to close the C#…
godot-ui-designer
Use this agent when the user needs to build or refactor user interfaces in Godot 4.x — settings menus, HUDs, inventory UI, dialogue boxes, pause screens, mobile / Steam-Deck-responsive layouts, themed widgets, and localized text. The agent always uses Control nodes (never Node2D for UI), drives layout via containers…
planner
Plan execution: turn approved intent/specs into a sequenced plan scaled to size. Full subagent.