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 makigjuro/cloudstack-ai-plugins --skill dotnet-testing-conventionsgit clone --depth 1 https://github.com/makigjuro/cloudstack-ai-pluginsWrote 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/makigjuro/cloudstack-ai-plugins/dotnet-testing-conventions)<a href="https://agentmods.dev/skills/makigjuro/cloudstack-ai-plugins/dotnet-testing-conventions"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/dotnet-testing-conventions/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/makigjuro/cloudstack-ai-plugins/dotnet-testing-conventions"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/dotnet-testing-conventions.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.00041 | $0.00372 |
| Opus 5.5 | $0.00016 | $0.00149 |
| Sonnet 5.5 | $0.00008 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
dotnet-testing-conventions 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 3d 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.
What it actually says
Testing Rules
Unit Tests
- xUnit with
[Fact]for single cases,[Theory]with[InlineData]for parameterized - NSubstitute for mocking:
var repo = Substitute.For<IOrderRepository>(); - FluentAssertions for assertions:
result.Should().BeSuccess(),result.Value.Should().NotBeNull() - Arrange-Act-Assert pattern with clear sections
- Verify calls:
repo.Received(1).AddAsync(Arg.Any<Order>(), Arg.Any<CancellationToken>())
Integration Tests
- Custom
WebApplicationFactory<Program>subclass per service - Implements
IAsyncLifetimefor setup/teardown - Testcontainers for PostgreSQL (or TimescaleDB if used)
CreateAuthenticatedClient()returnsHttpClientwith default auth headers- Database reset between tests:
EnsureDeletedAsync()thenEnsureCreatedAsync() - Use
PostAsJsonAsync(),GetAsync(),DeleteAsync()on HttpClient - Assert on HTTP status codes and deserialized response bodies
Test Organization
- Unit tests:
tests/{Namespace}.Domain.Tests/ - Integration tests:
tests/{ServiceName}.Tests.Integration/ - Integration tests filtered by
Category=Integration
Naming
- Test classes:
{ClassUnderTest}Tests - Test methods:
{Method}_{Scenario}_{ExpectedResult}or descriptive sentence - Example:
Handle_WhenOrderExists_ReturnsConflict
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.
- 3d ago First seen · 36 lines · 41 tokens per session scan A f386124fed8d
dotnet-testing-conventions is a skill published in the GitHub repository makigjuro/cloudstack-ai-plugins (1 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 372 once invoked, about $0.0002 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-10-21.
Other skills, from other repositories
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
ios-testing-patterns
XCTest and XCUITest execution workflows and flaky test detection patterns.
testing-assistant
Manages testing lifecycle including unit tests, integration tests, validation, and quality assurance.
verify
Verification loop — lint -> typecheck -> unit -> integration -> e2e.
check-coverage
Comprehensive assessment of Unit / Integration / E2E three-layer test coverage, identify gaps and provide actionable recommendations.
opa
Generate, test, validate, explain, and debug OPA (Open Policy Agent) Rego policies and Conftest configurations. Covers deny/warn/violation rules, unit tests, regal linting, conftest fmt, namespace design, input shape analysis, and GitHub Actions integration. Use when asked to "write a policy", "test a rego file"…