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 skills add StefanTheCode/dotnet-ai-toolkit --skill integration-test-setupgit clone --depth 1 https://github.com/StefanTheCode/dotnet-ai-toolkitWrote 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/skills/stefanthecode/dotnet-ai-toolkit/integration-test-setup)<a href="https://agentmods.dev/skills/stefanthecode/dotnet-ai-toolkit/integration-test-setup"><img src="https://agentmods.dev/badge/skills/stefanthecode/dotnet-ai-toolkit/integration-test-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/stefanthecode/dotnet-ai-toolkit/integration-test-setup"><img src="https://agentmods.dev/badge/skills/stefanthecode/dotnet-ai-toolkit/integration-test-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 122 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- high Memory Poisoning · line 123 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.1 | $0.00110 | $0.01200 |
| Opus 5.5 | $0.00044 | $0.00480 |
| Sonnet 5.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 2mo 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.
- 2mo 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 (26 stars, last pushed 2mo ago), licensed MIT. It adds 110 tokens to every session and 1,200 once invoked, about $0.0004 per session on Opus 5.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.
integration-test-setup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| integration-test-setupStefanTheCode/dotnet-ai-toolkit | Skill | 26 | 2mo ago | MIT | A | 110 | Claude Code |
| verify-omnigentomnigent-ai/omnigent | Skill | 11k | yesterday | Apache-2.0 | A | 100 | Claude Code, Codex |
| test-masterJeffallan/claude-skills | Skill | 12k | 7d ago | MIT | A | 104 | Claude Code |
| eval-dataset-designbojieli/ai-agent-book | Skill | 57k | 29d ago | Apache-2.0 | A | 138 | Claude Code, Codex |
| dogfoodcallstack/agent-device | Skill | 5.3k | yesterday | MIT | A | 55 | Claude Code |
| cua-driverdavidondrej/skills | Skill | 4.3k | 3d ago | MIT | A | 68 | Claude Code, Codex |
| test-warp-uiwarpdotdev/warp | Skill | 66k | yesterday | AGPL-3.0 | A | 55 | Claude Code |