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 skills/microsoft/datafactory.mcp/datafactory.architecturenpx skills add microsoft/DataFactory.MCP --skill datafactory.architecturegit clone --depth 1 https://github.com/microsoft/DataFactory.MCPWhat 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.00032 | $0.00977 |
| Opus 5 | $0.00016 | $0.00489 |
| Sonnet 5 | $0.00006 | $0.00195 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
datafactory.architecture 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 2d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DataFactory.MCP Architecture
For the full architecture reference, see docs/ARCHITECTURE.md.
Project Structure
DataFactory.MCP/ — Main MCP server (stdio transport, entry point)
DataFactory.MCP.Core/ — Core library (all business logic)
├── Abstractions/ — Interfaces and contracts
├── Configuration/ — App configuration classes
├── Extensions/ — Extension methods and DI registration
├── Infrastructure/ — Cross-cutting concerns (HTTP, logging)
├── Models/ — Data models and DTOs
├── Parsing/ — Input parsing utilities
├── Resources/ — Embedded resources
├── Services/ — Fabric API service clients
├── Tools/ — MCP tool implementations
└── Validation/ — Input validation
DataFactory.MCP.Http/ — HTTP transport layer (AspNetCore)
DataFactory.MCP.Tests/ — Test suite (xUnit)
DataFactory.WindowsMCP/ — Windows-specific MCP implementation
claude-skills/ — Claude skill definitions (RAG pattern)
docs/ — Feature documentation
evals/ — Evaluation test scenarios
Layered Architecture
AI Chat Interface (VS Code, Visual Studio)
│ MCP Protocol (JSON-RPC over stdio)
▼
┌─ MCP Tools Layer ──────────────────────────────┐
│ AuthenticationTool, GatewayTool, │
│ ConnectionsTool, WorkspacesTool, │
│ Dataflow/*, Pipeline/*, CopyJob/*, │
│ CapacityTool, CreateConnectionUITool │
├─ Core Services Layer ──────────────────────────┤
│ AuthenticationService, FabricGatewayService, │
│ FabricConnectionService, FabricWorkspaceService│
│ FabricDataflowService, FabricPipelineService, │
│ FabricCopyJobService, FabricCapacityService, │
│ ValidationService, DataTransformationService │
├─ Infrastructure Layer ─────────────────────────┤
│ AuthenticatedHttpHandler, ApiVersionConfig, │
│ McpSessionAccessor, BackgroundTasks │
├─ Abstractions Layer ───────────────────────────┤
│ Interfaces for all services │
├─ Models Layer ─────────────────────────────────┤
│ DTOs, request/response types, enums │
└─────────────────────────────────────────────────┘
│ Fabric REST APIs (with Azure AD tokens)
▼
Microsoft Fabric / Power BI Service
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.
- 2d ago First seen · 92 lines · 32 tokens per session scan A 3dfb62646f0d
datafactory.architecture is a skill published in the GitHub repository microsoft/DataFactory.MCP (42 stars, last pushed 20d ago), licensed MIT. It adds 32 tokens to every session and 977 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…