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/stefanthecode/dotnet-ai-toolkit/integration-test-setupnpx skills add StefanTheCode/dotnet-ai-toolkit --skill integration-test-setupgit clone --depth 1 https://github.com/StefanTheCode/dotnet-ai-toolkitWhat 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.00110 | $0.01200 |
| Opus 5 | $0.00055 | $0.00600 |
| Sonnet 5 | $0.00022 | $0.00240 |
| Haiku 4.5 | $0.00011 | $0.00120 |
Grade A, and why
integration-test-setup 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Test Setup (.NET)
Stand up real integration tests for an ASP.NET Core API: a custom WebApplicationFactory, a real database via Testcontainers, and a sample test that exercises the full HTTP pipeline.
Input — point it at your project
Point this at the API project or repo, not a pasted file — inspect what exists first:
- A project or repo root — find
Program.cs, the endpoints, and any existing integration-test project. - A GitHub URL — clone first, then inspect:
git clone --depth 1 <url> /tmp/repo && cd /tmp/repo
Discover the surface yourself before generating, e.g.:
find <target> -name Program.cs | grep -vi "/obj/\|/bin/"
grep -rn "MapGet\|MapPost\|MapPut\|MapDelete\|: ControllerBase\|ICarterModule" --include=*.cs <target> | head
find <target> -iname "*IntegrationTest*" -o -iname "*.IntegrationTests.csproj"
If an integration-test project already exists, review and extend it (e.g. flag EnsureDbCreated vs MigrateAsync, unpinned images, missing state reset) instead of scaffolding from scratch. Pick a representative endpoint to produce the first test.
When this runs
The user wants tests that exercise the app for real — routing, DI, middleware, EF Core against an actual database — not mocked units. Inspect the project, then confirm the database (default PostgreSQL via Testcontainers; support SQL Server) only if you can't infer it from the existing setup.
Packages
dotnet add package Microsoft.AspNetCore.Mvc.Testing
dotnet add package Testcontainers.PostgreSql # or Testcontainers.MsSql
dotnet add package xunit
dotnet add package FluentAssertions
dotnet add package Respawn # reset DB state between tests
The factory (real DB swapped in)
public class IntegrationTestFactory : WebApplicationFactory<Program>, IAsyncLifetime
{
private readonly PostgreSqlContainer _db = new PostgreSqlBuilder()
.WithImage("postgres:16-alpine")
.Build();
protected override void ConfigureWebHost(IWebHostBuilder builder)
{
builder.ConfigureTestServices(services =>
{
// Remove the app's registered DbContext and point it at the container
services.RemoveAll<DbContextOptions<AppDbContext>>();
services.AddDbContext<AppDbContext>(o => o.UseNpgsql(_db.GetConnectionString()));
});
}
public async Task InitializeAsync()
{
await _db.StartAsync();
using var scope = Services.CreateScope();
var ctx = scope.ServiceProvider.GetRequiredService<AppDbContext>();
await ctx.Database.MigrateAsync();
}
public new async Task DisposeAsync() => await _db.DisposeAsync();
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 125 lines · 110 tokens per session scan A 7dcf86ef1d73
integration-test-setup is a skill published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (19 stars, last pushed 23d ago), licensed MIT. It adds 110 tokens to every session and 1,200 once invoked, about $0.0006 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.