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/tester.testing-patternsnpx skills add microsoft/DataFactory.MCP --skill tester.testing-patternsgit 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.00031 | $0.00598 |
| Opus 5 | $0.00015 | $0.00299 |
| Sonnet 5 | $0.00006 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
tester.testing-patterns 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing in DataFactory.MCP
Test Stack
- Framework: xUnit (
[Fact],[Theory],[InlineData]) - Runner:
xunit.runner.visualstudio - Skippable:
Xunit.SkippableFact([SkippableFact],Skip.If(...)) - Coverage: coverlet
- Target: net10.0
Test Location
All tests live in DataFactory.MCP.Tests/.
Commands
| Task | Command |
|---|---|
| Run all | dotnet test |
| Verbose | dotnet test -v normal |
| Filter | dotnet test --filter "FullyQualifiedName~TestName" |
| Coverage | dotnet test --collect:"XPlat Code Coverage" |
Naming Convention
MethodName_Scenario_ExpectedResult
Examples:
Authenticate_WithValidCredentials_ReturnsTokenListGateways_WhenNotAuthenticated_ThrowsExceptionCreateConnection_WithInvalidType_ReturnsError
Test Patterns
Unit Test (Arrange-Act-Assert)
public class MyServiceTests
{
[Fact]
public void MethodName_Scenario_ExpectedResult()
{
// Arrange
var service = new MyService();
// Act
var result = service.DoSomething();
// Assert
Assert.NotNull(result);
Assert.Equal("expected", result.Value);
}
}
Parameterized Tests
[Theory]
[InlineData("input1", "expected1")]
[InlineData("input2", "expected2")]
public void MethodName_WithVariousInputs_ReturnsExpected(string input, string expected)
{
var result = MyService.Process(input);
Assert.Equal(expected, result);
}
Skippable Tests (for environment-dependent tests)
[SkippableFact]
public void IntegrationTest_RequiresAuth()
{
Skip.If(string.IsNullOrEmpty(Environment.GetEnvironmentVariable("AZURE_CLIENT_ID")),
"Requires Azure credentials");
// test body
}
What to Test
- Tools: Parameter validation, response formatting, error handling
- Services: API call construction, response parsing, error translation
- Models: Serialization/deserialization roundtrips
- Edge cases: Null inputs, empty collections, unauthenticated state, API errors
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 · 100 lines · 31 tokens per session scan A 9d7364143ec2
tester.testing-patterns is a skill published in the GitHub repository microsoft/DataFactory.MCP (42 stars, last pushed 20d ago), licensed MIT. It adds 31 tokens to every session and 598 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.