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 fpindej/netrock --skill add-testgit clone --depth 1 https://github.com/fpindej/netrockWrote 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/fpindej/netrock/add-test)<a href="https://agentmods.dev/skills/fpindej/netrock/add-test"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/add-test/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/fpindej/netrock/add-test"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/add-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00006 | $0.01015 |
| Opus 5.5 | $0.00002 | $0.00406 |
| Sonnet 5.5 | $0.00001 | $0.00203 |
| Haiku 4.5 | $0.00001 | $0.00102 |
Grade A, and why
add-test 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 1mo 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adds tests. Specify test type or infer from context.
Unit Test
For pure logic in Shared, Domain, or Application layers.
- Create
src/backend/tests/MyProject.Unit.Tests/{Layer}/{ClassUnderTest}Tests.cs - Structure:
{Method}_{Scenario}_{Expected}naming - No mocking, no DI - test pure inputs and outputs
- Verify:
dotnet test src/backend/tests/MyProject.Unit.Tests -c Release
Component Test
For service business logic with mocked dependencies.
- Create
src/backend/tests/MyProject.Component.Tests/Services/{Service}Tests.cs - Create mocks in constructor:
private readonly MyProjectDbContext _dbContext = TestDbContextFactory.Create(); private readonly IOrderRepository _orderRepo = Substitute.For<IOrderRepository>(); private readonly HybridCache _cache = Substitute.For<HybridCache>(); - For Identity:
IdentityMockHelpers.CreateMockUserManager()/CreateMockRoleManager() - Assert on
Result:Assert.True(result.IsSuccess); Assert.Equal(expectedId, result.Value); - Verify:
dotnet test src/backend/tests/MyProject.Component.Tests -c Release
API Integration Test
For testing the full HTTP pipeline (routes, auth, validation, status codes).
- Create
src/backend/tests/MyProject.Api.Tests/Controllers/{Controller}Tests.cs - Structure:
public class OrdersControllerTests : IClassFixture<CustomWebApplicationFactory>, IDisposable { private readonly CustomWebApplicationFactory _factory; private readonly HttpClient _client; public OrdersControllerTests(CustomWebApplicationFactory factory) { _factory = factory; _client = factory.CreateClient(); } public void Dispose() => _client.Dispose(); } - Auth per-request via
Authorizationheader:"Test"- basic authenticated userTestAuth.WithPermissions(AppPermissions.Users.View)- specific permissionsTestAuth.Superuser()- bypasses all checks- No header - unauthenticated (401)
- Configure mock returns:
_factory.AdminService.Method(...).Returns(...); - If service interface not mocked in
CustomWebApplicationFactory, add it there first - For 200/201 responses, add response contract assertions using frozen records in
Contracts/ResponseContracts.cs - Verify:
dotnet test src/backend/tests/MyProject.Api.Tests -c Release
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.
- 1mo ago First seen · 114 lines · 6 tokens per session scan A 0f4305ce7bde
add-test is a skill published in the GitHub repository fpindej/netrock (234 stars, last pushed 5d ago), licensed MIT. It adds 6 tokens to every session and 1,015 once invoked, about $0.0000 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.
Other skills, from other repositories
python-testing
Guidelines for Python testing using pytest and pytest-asyncio. Use when writing or debugging backend tests.
react-testing
Frontend testing standards using Vitest, React Testing Library, and Playwright. Use when writing UI tests.
author-test
Generate a test given sample. Parameters: C# SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; the sample to use as a starting point for the test.
pytest-suite
Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.
testing-patterns
Testing patterns for Spring Boot - JUnit 5, Mockito, MockMvc, Testcontainers, positive and negative test cases. Use when user asks about testing, writing tests, test coverage, or test failures.
test-runner
For a code change, pick the right test tier by change surface, run apc test with baseline diff, and report only NEW reds vs baseline back to the task's acceptance criterion. Separates envblocked from SUT red so a broken machine never fails the code.