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 cuongtl1992/vibe-skills --skill dotnet-tddgit clone --depth 1 https://github.com/cuongtl1992/vibe-skillsWrote 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/cuongtl1992/vibe-skills/dotnet-tdd)<a href="https://agentmods.dev/skills/cuongtl1992/vibe-skills/dotnet-tdd"><img src="https://agentmods.dev/badge/skills/cuongtl1992/vibe-skills/dotnet-tdd/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/cuongtl1992/vibe-skills/dotnet-tdd"><img src="https://agentmods.dev/badge/skills/cuongtl1992/vibe-skills/dotnet-tdd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00108 | $0.01627 |
| Opus 5 | $0.00054 | $0.00813 |
| Sonnet 5 | $0.00022 | $0.00325 |
| Haiku 4.5 | $0.00011 | $0.00163 |
Grade A, and why
dotnet-tdd 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 12d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Core TDD Workflow
Test-Driven Development workflow for C# / .NET Core using xUnit + Moq + FluentAssertions.
Every piece of code follows the Plan → Test (RED) → Implement (GREEN + REFACTOR) → Review cycle.
Phase 1: PLAN
Analyze the requirement before writing any code or test.
- Understand the requirement — what is the expected behavior?
- Identify the component type — which test strategy applies? (see matrix below)
- List test cases — happy path, edge cases, error cases
- Define the public API — method signatures, input/output types
Component → Test Strategy Matrix
| Component | What to test | Mocking strategy |
|---|---|---|
| Aggregate/Entity | Factory methods, behavior, invariants, domain events | No mocks — pure domain logic |
| Value Object | Creation validation, equality, behavior | No mocks — pure logic |
| UseCaseHandler | Business flow, repository calls, UoW commit, errors | Mock repositories, UoW, domain services |
| QueryHandler | SQL correctness, mapping, null handling | Mock IDbConnection (or integration test) |
| Domain Service | Cross-aggregate logic | Mock repositories |
| Application Service | Orchestration, validation | Mock dependencies |
Example Plan Output
Feature: Create Invoice UseCase
Test Cases:
1. ✅ Should create invoice with valid data and commit
2. ✅ Should raise InvoiceCreatedEvent domain event
3. ✅ Should call repository.AddAsync with correct entity
4. ❌ Should throw when buyer tax code is empty
5. ❌ Should throw when amount is negative
6. 🔄 Should handle concurrent creation (idempotency)
Phase 2: TEST (RED)
Write failing tests BEFORE any implementation. Tests must fail for the RIGHT reason.
Test Project Structure
tests/{Module}.{Layer}.Tests/
├── UseCaseHandlers/
│ └── CreateInvoiceUseCaseHandlerTests.cs
├── QueryHandlers/
│ └── GetInvoiceByIdQueryHandlerTests.cs
├── Entities/
│ └── InvoiceTests.cs
├── ValueObjects/
│ └── MoneyTests.cs
└── _usings.cs
What ships with it
4 files 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.
- 12d ago First seen · 205 lines · 108 tokens per session scan A 7c6001e00b0a
dotnet-tdd is a skill published in the GitHub repository cuongtl1992/vibe-skills (10 stars, last pushed 5mo ago), licensed MIT. It adds 108 tokens to every session and 1,627 once invoked, about $0.0005 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-31.
Other skills, from other repositories
nw-fp-fsharp
F# language-specific patterns, Railway-Oriented Programming, and Computation Expressions.
tdd
Guided test-driven development workflow for .NET 10 using xUnit v3, WebApplicationFactory, Testcontainers, and Verify snapshots. Follows the strict red-green-refactor cycle. Use when: "TDD", "test-driven", "let's TDD this", "red green refactor", "write the test first", or when building a feature with clear acceptance…
test-driven-development
Drives .NET/C# development with tests — RED/GREEN/REFACTOR with xUnit (v2 or v3) or MSTest, the Prove-It Pattern for bug fixes, the test pyramid with WebApplicationFactory for integration and Playwright/Avalonia.Headless for E2E. Supports both VSTest and Microsoft.Testing.Platform (MTP) runners. Use when implementing…
csharp-tdd-develop
A guide for developing C# and .NET software with test-driven development, or TDD, where tests are written before the code. It follows the Red-Green-Refactor cycle and delegates work to sub-agents.
kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.